I had created a test forum with two web_only containers, the mail-receiver container, Postgres and Redis on a Docker network. The two web containers nginx’s were fronted by HAProxy. They worked well, but i found on rebuilding one of the two web containers there was always a small amount of downtime …

Why don’t you redispatch to the next server on a 503 ?

nice! that would be good. Also, do you have any suggestions about sidekiq? I don’t see sidekiq at all in discourse_docker/samples at main · discourse/discourse_docker · GitHub which lead to me making the following changes to either yml app1.yml ## Remember, this is YAML syntax - you can only have…

For anyone running multiple web containers, one extra piece to think about is where Sidekiq runs. 503s only affect web requests, but if Sidekiq is down your site will quietly stop handling background jobs (emails, digests, badges, webhooks). A neat way to handle this is to give Sidekiq its own cont…

Transient 503s after ./launcher rebuild appN when they’re fronted by HAProxy

Support Self-hosting

tobiaseigen (Tobias Eigen) September 26, 2025, 5:04pm 5

I moved this to #installation:hosting as it seems to be an open ended conversation. Let’s avoid creating these in Support.

Topic		Replies	Views
"Ensure sidekiq is running." when it is definitely running Self-hosting	19	7874	October 24, 2015
Sidekiq heartbeat test failed, restarting Self-hosting	12	2104	February 11, 2020
Show an error page when rebuild Feature	8	1730	December 4, 2025
Issue with new update: debugging options Self-hosting	16	327	August 30, 2024
High Availability Self-hosting	11	2360	July 15, 2023

Transient 503s after ./launcher rebuild appN when they’re fronted by HAProxy

Related topics