Differences

This shows you the differences between two versions of the page.

--- litespeed_wiki:cloudlinux:node.js_selector [2020/01/13 18:42]
Lisa Clarke [How LiteSpeed works with Node.js selector?] Proofreading
+++ litespeed_wiki:cloudlinux:node.js_selector [2020/01/29 15:11]
Shivam Saluja [Troubleshooting]
@@ Line 12: / Line 12: @@
 ===== How LiteSpeed Works with NodeJS Selector =====
-For a NodeJS application managed by CloudLinux NodeJS selector, LSWS does an automatic ''ws://'' proxy to the NodeJS backend, if the request does a WebSocket upgrade. No extra configuration required.
+For a NodeJS application managed by CloudLinux NodeJS selector, LSWS does an automatic ''<nowiki>ws://</nowiki>'' proxy to the NodeJS backend, if the request does a WebSocket upgrade. No extra configuration required.
-When direct connecting to a NodeJS server, test with <code>ws://...</code>.
+When direct connecting to a NodeJS server, test with
+<code>ws://...</code>.
-When going through a LSWS HTTPS proxy server, use <code>wss://...</code>.
+When going through a LSWS HTTPS proxy server, use
+<code>wss://...</code>.
 When a NodeJS server is started through LSWS NodeJS selector integration (mod_passenger), the TCP socket is replaced with an auto-generated Unix domain socket, hence direct access the TCP port may fail.
@@ Line 53: / Line 55: @@
 You can also verify that the 'Litespeed Node.js Service' is running.  From a command prompt enter:
-<code>ps -ef|grep Node</code>
+<code>ps -ef|grep node</code>
-One of the displayed running processes should be <code>Litespeed Node.js Service</code>
+One of the displayed running processes should be shown like this <code>lsnode:/home/USER/public_html/APPDIR/</code>
 When troubleshooting, you may want to bring up a stand-alone Node.js server and verify that the software works through //that//, to be sure that the problem is not in the Javascript itself.