FrederikBaerentsen/BrickTracker
8
20
Fork 12
Code Issues 16 Pull Requests Actions Packages Projects 1 Releases 11 Wiki Activity

[Bug] Reverse proxy causes socket to disconnect #90

New Issue
Closed
opened 2025-09-17 19:55:48 +02:00 by FrederikBaerentsen · 9 comments
FrederikBaerentsen commented 2025-09-17 19:55:48 +02:00
Owner
Copy Link
Copy Source

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.

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/SecurityKind/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
Author
Owner
Copy Link
Copy Source

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.

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
Copy Link
Copy Source

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

I have the same issue using NPM. it's really only an issue with trying to do set refreshes.
Watever commented 2025-11-23 22:31:47 +01:00
Copy Link
Copy Source

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
Copy Link
Copy Source

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
Copy Link
Copy Source

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
Copy Link
Copy Source

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.
joshmans commented 2025-12-26 04:27:12 +01:00
Copy Link
Copy Source

Note that this issue is fixed in 1.3.x

Note that this issue is fixed in 1.3.x
joshmans commented 2025-12-26 04:39:07 +01:00
Copy Link
Copy Source

Note that this issue is fixed in 1.3.x

scratch that, it looked like it was but it was just delayed in displaying the socket disconnect message

> Note that this issue is fixed in 1.3.x scratch that, it looked like it was but it was just delayed in displaying the socket disconnect message
FrederikBaerentsen added the
Priority
Medium
 label 2026-01-01 17:02:18 +01:00
FrederikBaerentsen commented 2026-02-18 16:39:47 +01:00
Author
Owner
Copy Link
Copy Source

After investigating this further, I believe the root cause is basic auth not being properly passed to WebSocket connections on iOS.

I switched my authentication from basic auth to Authelia and the issue is completely resolved. I would suggest to use a session/cookie-based authentication solution (Authelia, Authentik, OAuth proxy, etc.) instead of basic auth when running behind a reverse proxy.

Closing this for now, feel free to reopen if the issue still arise with another auth method.

After investigating this further, I believe the root cause is basic auth not being properly passed to WebSocket connections on iOS. I switched my authentication from basic auth to Authelia and the issue is completely resolved. I would suggest to use a session/cookie-based authentication solution (Authelia, Authentik, OAuth proxy, etc.) instead of basic auth when running behind a reverse proxy. Closing this for now, feel free to reopen if the issue still arise with another auth method.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Compat/Breaking
Breaking change that won't be backward compatible
 Kind/Bug
Something is not working
 Kind/Documentation
Documentation changes
 Kind/Enhancement
Improve existing functionality
 Kind/Feature
New functionality
 Kind/Security
This is security issue
 Kind/Testing
Issue or pull request related to testing
 Out of Scope
Request is out of scope
Priority
Critical
The priority is critical
Priority
High
The priority is high
Priority
Low
The priority is low
Priority
Medium
The priority is medium
Reviewed
Confirmed
Issue has been confirmed
Reviewed
Duplicate
This issue or pull request already exists
Reviewed
Invalid
Invalid issue
Reviewed
Won't Fix
This issue won't be fixed
Status
Abandoned
Somebody has started to work on this but abandoned work
Status
Blocked
Something is blocking this issue or pull request
Status
Need More Info
Feedback is required to reproduce issue or to continue work
Unraid
Unsupported/Can't help
No labels Kind/Bug Kind/Security
Priority
Medium
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
FrederikBaerentsen
No Assignees FrederikBaerentsen
4 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: FrederikBaerentsen/BrickTracker#90