You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Probably another quiet update to the websockets standard that will break stuff when Chrome+Firefox decides to be a hardass. Seeing this in the JS console
socket.io.js:8 WebSocket connection to 'wss://sync.wetfish.net/socket.io/?EIO=3&transport=websocket&sid={redacted}' failed: Error during WebSocket handshake: 'Connection' header value must contain 'Upgrade'
The text was updated successfully, but these errors were encountered:
i think the problem is due to the nginx configuration for ssl isn't proxy_passed, you should add proxy_ to the cert, key, and whatever else related to the ssl configuration i think. i looked over the server configuration you sent me and i think it might be solved by following that tutorial, however i'll need to test on my local with self signed cert, but if you want to now, you could try it.
bleah, I shouldn't be surprised it's case-sensitive. This looks like a problem with nginx not sync; we can resolve this issue by adding set-up instructions in the readme.md. If this were a ticketing system I'd downgrade this to "minor."
Probably another quiet update to the websockets standard that will break stuff when Chrome+Firefox decides to be a hardass. Seeing this in the JS console
socket.io.js:8 WebSocket connection to 'wss://sync.wetfish.net/socket.io/?EIO=3&transport=websocket&sid={redacted}' failed: Error during WebSocket handshake: 'Connection' header value must contain 'Upgrade'
The text was updated successfully, but these errors were encountered: