Skip to content
Discussion options

You must be logged in to vote

The documented HA path is multiple Rocket.Chat instances behind Traefik/a load balancer, all using the same MongoDB replica set; the docs also recommend a 3-member MongoDB replica set for HA and object storage for uploads. (docs.rocket.chat) (docs.rocket.chat)

For an unpaid/active-passive-style setup, the practical approach is a warm standby, not true failover: keep a second host ready with the same Rocket.Chat Docker config and version, keep Rocket.Chat stopped there, and have it point to the same external MongoDB replica set and shared/object file storage. If the primary host dies, move DNS / reverse proxy / VIP to the standby and start the container.

The important bit is that the data …

Replies: 1 comment 1 reply

Comment options

You must be logged in to vote
1 reply
@jt13890
Comment options

Answer selected by jt13890
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
2 participants