I have a problem with websockets not working after an OLS graceful restart.
Using OpenLiteSpeed Node.js template on hostinger Ubuntu.
On first server start, multiple clients (Win32 apps using WinHttp) can connect to the node.js app and open a websocket without problems. Each client connects to a different URL. The websocket is kept alive indefinitely with ping/pong. The client apps can be restarted numerous times if desired and will reconnect every time without any problems.
However, once the server is restarted (graceful restart via OLS webadmin panel), then no clients can connect. Normal https operations such as get/post etc still work, but attempts to perform an upgrade to a websocket get no response. All clients behave this way. I have also tested with a POSTMAN client and it behaves the same. Restarting the clients has no effect.
If I restart the OLS server a second time, then all clients can once again connect and everything is fine again.
Further testing has shown that if any client has had an open websocket during the PREVIOUS server instance, then none will connect in the CURRENT instance.
I have tried setting Graceful Restart Timeout to 0 (blank) but this made no difference.
The websocket is built into the node app, I am not using the OLS VHost ->Websocket Proxy. Although I have tried doing it that way as per the docs and got the same result.
The node.js app running locally on a development server without OLS does not have this problem.
Any suggestions/help appreciated. Thanks.
Using OpenLiteSpeed Node.js template on hostinger Ubuntu.
On first server start, multiple clients (Win32 apps using WinHttp) can connect to the node.js app and open a websocket without problems. Each client connects to a different URL. The websocket is kept alive indefinitely with ping/pong. The client apps can be restarted numerous times if desired and will reconnect every time without any problems.
However, once the server is restarted (graceful restart via OLS webadmin panel), then no clients can connect. Normal https operations such as get/post etc still work, but attempts to perform an upgrade to a websocket get no response. All clients behave this way. I have also tested with a POSTMAN client and it behaves the same. Restarting the clients has no effect.
If I restart the OLS server a second time, then all clients can once again connect and everything is fine again.
Further testing has shown that if any client has had an open websocket during the PREVIOUS server instance, then none will connect in the CURRENT instance.
I have tried setting Graceful Restart Timeout to 0 (blank) but this made no difference.
The websocket is built into the node app, I am not using the OLS VHost ->Websocket Proxy. Although I have tried doing it that way as per the docs and got the same result.
The node.js app running locally on a development server without OLS does not have this problem.
Any suggestions/help appreciated. Thanks.
