I received email notifications from Rocket Chat that my workspace would stop receiving notifications from May 1st unless I updated to version 7 before 30th April. I did the upgrade on April the 10th (currently 7.5.0).
However, my notifications appear to have been cut off anyway - I tried to contact their support desk but they don’t provide support for Community servers, and their automated response suggested I try here. I get the same response if I reply to the email notifications.
Does anyone know why this might have happened or what I should do to get my notifications restored (or if that is even possible)?
I’ll jump in here because I have exactly the same problem. We also updated at the end of April to 7.5 because I also got that message. But in May we did not receive any push notification. I checked the settings as told on various support sites, switched off and on the push notifications, but nothing worked here. So do you have any updates on this topic?
Server 7.5.0
Engine 1.50.0
Node 22.13.1
Mongo 6.0.19
100 Users, typically about 3000-4000 notifications per Month this year (up to April, May - 0)
Working for days now, as soon as I published my post, I found a solution by myself. So maybe it helps someone else:
We are running rocket chat on a ubuntu server, installed and updated to V. 7.5 via snaps.
While reading the docs for the 10th time or so the three magic letters “SSL” jumped into my eyes and this turned out to be the clue: During updating from V6 to V7 the SSL settings obviously got lost. So I checked the presence of my certificates in /etc/ssl (still there), I checked the contents of the caddy file /var/snap/rocketchat-server/current/Caddyfile (still ok) and finally reset the site url with “sudo snap set rocketchat-server siteurl=https://aaa.bbb.com:3000”. After a system restart (maybe only a rocket chat restarts is enough) the push notifications worked like a charm again.
I did not really notice, that ssl was gone because we are using haproxy as a reverse proxy, so the connections were still ssl’ed. On some day after the update somebody called me and told me that rocket chat did not work, I checked haproxy and unchecked the SSL-Offloading box. But I did not connect this event to the update of rocket chat, I just thought I had messed up the config somehow.
Now that I again and again read SSL in the docs, it ring a bell and - voila, push notes are pushing again…
For me, I didn’t need to reset the siteurl (and in case anyone else tries it - adding :3000 broke it because I’m using the default Caddy proxy), but instead needed to run sudo systemctl enable --now snap.rocketchat-server.rocketchat-caddy followed by sudo snap restart rocketchat-server - that immediately restored notifications.
Never would have got there without you figuring that out - thanks very much!
I’m glad to help :-). But can somebody explain it somehow? I read the docs again (Deploy with Snaps) and there it says, that you can also use another http proxy than caddy. Which we did, I have haproxy installed (another machine in DMZ) which did the SSL encryption. The chat itself was working with no issues, also the certificate of haproxy was correct. Why did the push notifications not work?
I just hat another look at my configurtion, and I’m still more confused: according to the status, caddy is not running (any more) at the moment, and I cannot open rocketchat via https://192.168.10.215:3000, just via http. But via the domain and the reverse proxy it works. AND: The reverse proxy (haproxy) uses in the backend SSL to connect to rocketchat
haproxy config:
backend RocketChat_ipvANY
mode http
id 102
log global
timeout connect 30000
timeout server 30000
retries 3
load-server-state-from-file global
server RocketChat 192.168.10.215:3000 id 103 **ssl** verify none
Can somebody explain, why my setup is working right now? Or why I cannot open the chat via IP and HTTPS?
