WebSocket connection failed

[opiums9]

Hello! I'm trying to set up Revolt on a reverse proxy using nginx, but I get a WebSocket error.
Registration is successful, but an error occurs after attempting to log in.

Maybe I configured the server incorrectly?
I'm attaching screenshots of the configuration, any help would be helpful

[jared1ternet]

Hello,

I have exactly the same problem. I bypassed my reverse proxy and I still get the same error..

[ykatkus]

same problem here, could you guys fix it?

its actually a showstopper error :/

tried deploying on hetzner vsp, same as on ubuntu 24.04 vm.

as far as debugging the webclient i couldnt spot a difference in data between official app.revolt.chat and my self-hosted. so maybe it might be a server/proxy issue?!

[michelleDeko]

I'm having the same issue

[Apatkin]

Hello, I am getting the same error.
I access Revolt and register an account, providing an email and a name, after which I receive a message saying that the registration was successful. However, after entering the email and password, I get an error like the one in the screenshots above or an infinite loading loop. In the browser console, the following message appears.
Please let me know if you find a solution.

[jennso]

I was able to make it work, by changing ws:// to wss:// in the .toml config file, and enabling websocket support in my reverse proxy, I'm using, nginx proxy manager as proxy server.

though I'm still getting some websocket erros here and there like

[maxi1134]

I was able to make it work, by changing ws:// to wss:// in the .toml config file, and enabling websocket support in my reverse proxy, I'm using, nginx proxy manager as proxy server.

though I'm still getting some websocket erros here and there like

Could you share your entire Nginx proxy manager config?

[jennso]

Nothing special, I think I probably need to add some custom locations to make other things work.

[insertish]

Likely duplicate of #125

Please report back if instructions in last comment work, thanks!

[opiums9]

This issue has been fixed, see #125