# Discourse with reverse proxy manager

**URL:** https://meta.discourse.org/t/discourse-with-reverse-proxy-manager/387730
**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:** 3

<div class="post-metadata">

### 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, 8:37am UTC](https://meta.discourse.org/t/discourse-with-reverse-proxy-manager/387730/3 "2025-11-08T08:37:46Z")

</div>

Good news - nothing looks “broken.” yet. That 502 was almost certainly a **first-boot race** : Nginx tried your `/srv/status` before Unicorn was ready. If your logs show:

- `unicorn: run` ✅
- Rails booted ✅
- Nginx error at HH:MM:SS “connection refused” (likely _before_ Unicorn finished)

Let’s clear it up quickly.

> 

1. Try the status again (host → app2)

```plaintext
curl -sSI http://127.0.0.1:8002/srv/status

```

1. If it still shows 502, just restart Nginx in app2 and test from _inside_ the container:

```plaintext
docker exec -it app2 bash -lc 'sv restart nginx && sleep 2 && curl -sSI http://127.0.0.1/srv/status'

```

```plaintext
curl -sSI http://127.0.0.1:8002/srv/status

```

You should see `HTTP/1.1 200 OK`.

* * *

---

_[View the full topic](https://meta.discourse.org/t/discourse-with-reverse-proxy-manager/387730)._