Mobile app use instantly crashes server. Everything “just works” in a web browser.
- Version of Rocket.Chat Server: 5.4.4
- Operating System: Debian 11.6
- Deployment Method: snap
- Proxy: nginx
- Firewalls involved: Ubiquiti edgerouter
I’m setting up a second installation of Rocket.Chat for home use because I’ve enjoyed using it at work, and it seems like it would be a good “backup” to SMS as my wife and I are often in places where we have wi-fi but not cellular data.
Setup process: Installed Debian, apt install snapd, snap install rocketchat-server. Also tried with Ubuntu, selecting the rocketchat-server option during the OS install, but had the same result.
Host is a VM on Proxmox.
I’m having an issue with my Rocket.Chat server crashing immediately, and 100% reproducibly by logging in to it with the Android app, I haven’t tested the iOS app as I don’t have an iOS device. If I log in with a web browser, everything works fine.
I’ve used RC at work for about a year, and my work environment is mostly the same as my “at home” environment (a Proxmox host running an RC snap, reverse proxied by nginx, but the nginx proxy is behind a Cisco ASA instead of an edgerouter), and I’m trying to set up a RC server for family use.
My nginx proxy config file is identical on both installations, with the obvious exceptions of the hostname / IP I’m proxying. (eg. rc.work.tld vs rc.home.tld, being proxied to 10.0.0.20:3000 vs 192.168.1.20:3000)
My at work setup process was the same, I created a VM, installed the snap, and that was it, and it’s been working well for quite a while.
I’m not sure what logs I could look at to figure out why the server crashes when logging in with a mobile app, but doing anything on the mobile app “crashes” the Rocket.Chat snap, that might be the wrong word, but 100% of the time if I open the mobile app, the RC server can’t be reached on port 3000 without using the proxy or on 443 with the proxy.
If I’m logged in on a browser on one device (even as a different account) and open the mobile app, as soon as the app is open (even on a different network, for example over cellular data) the browser will show “Waiting for server connection, trying again in X seconds…” and stay like that forever until I close the mobile app. Once the mobile app is closed, the browser based interface comes back up in about 5-10 seconds. If I wasn’t logged in in a browser when opening the mobile app, I get the nginx 502 Bad Gateway error page that I would get if the server being proxied was “turned off”.
If I leave the mobile app open, I can connect to my server, log in, see the channel / user list (for about 1 second), but the top of the screen will then rapidly swap between “Waiting for network… / Updating… / Waiting for network… / Updating…”
I can happily post whatever logs might be useful to see why this is happening, but I don’t know how or where to find them.