Websocket connection can't authenticate #6654
-
On a fresh 0.75.2 docker based installation (everything default), I get this repeated message on the frontend: It does sometimes manage to authenticate, or at least the 'Authorization failed' message in the bottom right goes away, when this happens I get these logs in docker:
The last few messages are after reloading the page, which will cause the connection to fail again. No multiplayer messages are in the backend log afterwards (so the authentication seems to silently fail). Frontend has the message shown above. I am authenticating via google. I have tried quite a few configuration changes but nothing seems to help. Hopefully someone knows what's causing this! |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Ok, I'm not entirely sure what happened, but I think something went wrong with cache/dns cache and there was an additional layer of reverse-proxy (via bunnycdn) happening. After a browser restart everything seems to work. |
Beta Was this translation helpful? Give feedback.
Ok, I'm not entirely sure what happened, but I think something went wrong with cache/dns cache and there was an additional layer of reverse-proxy (via bunnycdn) happening. After a browser restart everything seems to work.