[Bug] Reverse proxy causes socket to disconnect #90

New Issue

FrederikBaerentsen · 2025-09-17T19:55:48+02:00

2025-09-17 19:55:48 +02:00

Using traefik myself and having a domain name and reverse proxy will cause multiple login windows (using traefik basic auth). If not logging in twice, the socket disconnects.

FrederikBaerentsen added the Kind/Security Kind/Bug labels 2025-09-17 19:55:48 +02:00

FrederikBaerentsen self-assigned this 2025-09-17 19:55:48 +02:00

FrederikBaerentsen commented

2025-09-17 20:17:56 +02:00

I've tried multiple options of parsing headers in traefik. I think socket connection needs to be changed in order to pass headers from traefik auth to the socket.

FrederikBaerentsen changed title from ~~Reverse proxy causes socket to disconnect~~ to [Bug] Reverse proxy causes socket to disconnect

2025-09-22 08:51:31 +02:00

joshmans commented

2025-10-19 05:23:11 +02:00

I have the same issue using NPM. it's really only an issue with trying to do set refreshes.

FrederikBaerentsen referenced this issue

2025-11-23 17:42:13 +01:00

Socket disconnected on Reverse Proxy (NGINX) #112

Watever commented

2025-11-23 22:31:47 +01:00

I have the same issue using NPM. it's really only an issue with trying to do set refreshes.

I am facing the same issue, have you found an solution or the cause of the issue ?
I have set the debug to true but I don't see much more problem.

> I have the same issue using NPM. it's really only an issue with trying to do set refreshes. I am facing the same issue, have you found an solution or the cause of the issue ? I have set the debug to true but I don't see much more problem.

joshmans commented

2025-11-23 23:35:56 +01:00

I have the same issue using NPM. it's really only an issue with trying to do set refreshes.

I am facing the same issue, have you found an solution or the cause of the issue ?
I have set the debug to true but I don't see much more problem.

My solution until the issue is resolved is to just do set refreshes directly/locally - w/o reverse proxy

> > I have the same issue using NPM. it's really only an issue with trying to do set refreshes. > > I am facing the same issue, have you found an solution or the cause of the issue ? > I have set the debug to true but I don't see much more problem. My solution until the issue is resolved is to just do set refreshes directly/locally - w/o reverse proxy

man0fsand commented

2025-12-12 10:46:49 +01:00

I have the same issue using NPM. it's really only an issue with trying to do set refreshes.

I am facing the same issue, have you found an solution or the cause of the issue ?
I have set the debug to true but I don't see much more problem.

My solution until the issue is resolved is to just do set refreshes directly/locally - w/o reverse proxy

Make sure Websockets Support is enabled. I use NPM and it works fine with that enabled

> > > I have the same issue using NPM. it's really only an issue with trying to do set refreshes. > > > > I am facing the same issue, have you found an solution or the cause of the issue ? > > I have set the debug to true but I don't see much more problem. > > My solution until the issue is resolved is to just do set refreshes directly/locally - w/o reverse proxy Make sure Websockets Support is enabled. I use NPM and it works fine with that enabled

joshmans commented

2025-12-12 10:53:26 +01:00

I have the same issue using NPM. it's really only an issue with trying to do set refreshes.

I am facing the same issue, have you found an solution or the cause of the issue ?
I have set the debug to true but I don't see much more problem.

My solution until the issue is resolved is to just do set refreshes directly/locally - w/o reverse proxy

Make sure Websockets Support is enabled. I use NPM and it works fine with that enabled

At least for me, it's enabled. Things don't really work at all if it's disabled.

> > > > I have the same issue using NPM. it's really only an issue with trying to do set refreshes. > > > > > > I am facing the same issue, have you found an solution or the cause of the issue ? > > > I have set the debug to true but I don't see much more problem. > > > > My solution until the issue is resolved is to just do set refreshes directly/locally - w/o reverse proxy > > Make sure Websockets Support is enabled. I use NPM and it works fine with that enabled At least for me, it's enabled. Things don't really work at all if it's disabled.

Sign in to join this conversation.

4 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#90