Open avelor opened 1 year ago
ive also updated from 5.4 to 6.4.2 i have multiple instances but in different clusters (1 instance of rocketchat per cluster) served by nginx and notifications are working, however status is seems to be broken now https://github.com/RocketChat/Rocket.Chat/issues/30721
Sound notifications work for us with Enterprise setup with one and multiple instances and with Community Edition using just a single instance.
Notifications using CE using multiple instances sometimes work, though. Maybe one out of four messages.
I'm still not sure if this is a CE feature or a bug. Our issue about it is https://github.com/RocketChat/Rocket.Chat/issues/28969 .
it seems that in 6x version RC needs another random tcp port on instances (transporter). It hasn't declared as env variable at docker-compose, exept dev environment - https://github.com/RocketChat/Rocket.Chat/blob/develop/docker-compose-local.yml
we've changed docker network to bridge and it seems to work now.
We decided to update RC from 5.x to lasted 6.4.2 version, and after update we saw that notifications doesn't work anymore - sound and desktop, with browser or electron client. Also we don't see at admin panel IP-address of any instance and it's hearbeat:
Does 6.4.2 supports such setup or it is some bug? it's like described here - https://docs.rocket.chat/deploy/deploy-rocket.chat/scaling-rocket.chat/running-multiple-instances only difference - we're using docker images. And 3.x, 4.x and 5.x worked smoothly with this setup.
Server Setup Information:
We tested update to 6.4.2 on test installation with only one app instance - and notifications work pretty well on it.