# Discourse with reverse proxy manager **URL:** \ **Category:** Self-hosting\ **Created:** [November 5, 2025, 11:09pm UTC](https://meta.discourse.org/t/discourse-with-reverse-proxy-manager/387730 "2025-11-05T23:09:58Z")\ **Posts on this page:** 1\ **Showing post:** 6
**Author:** ![Ethsim2](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ethsim2/32/522255_2.png) [@Ethsim2](https://meta.discourse.org/u/Ethsim2)\ **Post date:** [November 8, 2025, 12:42pm UTC](https://meta.discourse.org/t/discourse-with-reverse-proxy-manager/387730/6 "2025-11-08T12:42:45Z")
yes it worked, and then i announced the result in the following topic; > [@Transient 503s after ./launcher rebuild appN when they’re fronted by HAProxy](https://meta.discourse.org/t/transient-503s-after-launcher-rebuild-appn-when-they-re-fronted-by-haproxy/383179): > > 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 where 503 was returned. Fortunately, i found a mitigating workaround, but nothing perfect; before rebuilding app1, run echo "disable server be\_discourse/app1" | socat stdio /run/haproxy/admin.sock … --- _[View the full topic](https://meta.discourse.org/t/discourse-with-reverse-proxy-manager/387730)._