Socket disconnected on Reverse Proxy (NGINX) #112

Open
opened 2025-11-23 17:29:51 +01:00 by Watever · 2 comments

I am wondering if anyone was able to get the container work behind a reverse proxy ?

When I set my domain name behind a proxy, I cannot get it to connect. It only works when I am connected directly to the IP:PORT.
Not sure why it would do this.

I understood in error, that you have to wait, but if so, how long ?

I am wondering if anyone was able to get the container work behind a reverse proxy ? When I set my domain name behind a proxy, I cannot get it to connect. It only works when I am connected directly to the IP:PORT. Not sure why it would do this. I understood in error, that you have to wait, but if so, how long ?

Do you have the right env var set? You need BK_DOMAIN_NAME set.

I am using traefik with basic auth myself.

Check #90, as there’s a bug with basic auth and reverse proxies.

Do you have the right env var set? You need BK_DOMAIN_NAME set. I am using traefik with basic auth myself. Check #90, as there’s a bug with basic auth and reverse proxies.
FrederikBaerentsen added the Kind/Bug label 2025-11-23 17:42:32 +01:00

Make sure you have websocket support enabled

Make sure you have websocket support enabled
Sign in to join this conversation.
3 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#112