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…

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

HAProxyでフロントエンドにした際の、一時的な503エラー

サポートインストール

tobiaseigen (Tobias Eigen) 2025 年 9 月 26 日午後 5:04 5

これを Installation > Hosting に移動しました。これはオープンな会話のように思われるためです。Support でこのようなものを作成しないようにしましょう。

トピック		返信	表示
"Ensure sidekiq is running." when it is definitely running Self-hosting	18	7879	2015 年 10 月 2 日
Sidekiq heartbeat test failed, restarting Self-hosting	11	2111	2020 年 1 月 12 日
Show an error page when rebuild Feature	7	1731	2015 年 8 月 26 日
Issue with new update: debugging options Self-hosting	16	327	2024 年 8 月 30 日
High Availability Self-hosting	8	2360	2017 年 10 月 3 日

HAProxyでフロントエンドにした際の、一時的な503エラー

関連トピック