Nope that upgrade can be run multiple times without side effects.
Error during WebSocket handshake
-
Hi there,
I've got a little issue with my config I think.
here is the error code that I get on my console :
nodebb.min.js?453b4725-ea90-484c-899a-1e8f5b2a773c:5
WebSocket connection to 'wss://forum.DOMAINENAME.fr/socket.io/?EIO=3&transport=websocket&sid=wL_TdDFYPkoWqwmNAAAf' failed: Error during WebSocket handshake: Unexpected response code: 500What Am I doing wrong ?
Th xfor your help ^^
-
Anyone ?
-
Are you using CloudFlare? Nginx as a proxy?
-
@julian Will NodeBB not work if I use Nginx as a reverse proxy?
-
Yes, it will work fine.
-
@julian I'm using CloudFlare indeed.
If I'm not wrong, we're using apache2 as a proxy.
PS: sorry for the late answer.
-
@Yokokoyo Not 100% sure if CloudFlare proxy or rocket loader works with NodeBB. Please disable it (grey clouds) and try to see if this issue is resolved?
-
@julian said in Error during WebSocket handshake:
@Yokokoyo Not 100% sure if CloudFlare proxy or rocket loader works with NodeBB. Please disable it (grey clouds) and try to see if this issue is resolved?
I can stand for it that the cloudflare websocket proxy works fine with NodeBB. I'm using the free plan and it states that the volume of concurrent connections is low, but it didn't run in troubles.
However, disabling cloudflare protection by enabling the grey cloud is a great way to troubleshoot
-
you know it.I've heard they support it too, though need more empirical evidence before I change my stance
-
I've tryed to connect to my direct IP (so without cloudflare) and I've still got the same error.
-
In that case, I would suspect something in between causing interruptions with the websocket connection (e.g. ISP, firewall, etc). Sometimes setting up SSL helps, but no guarantees.
Without websockets, NodeBB will drop down to xhr-polling, which is fine functionality-wise, if a little slower.
-
You said you use Apache2 as a proxy. When setting it up: did you follow the documentation from here? I suspect that Websocket upgrade-requests are not correctly handled. In that case, no websocket-connection could be set up and thus the handshake will fail.
-
I'm quite sure I did, but juste in case I will check again.
