[Bug]: Socket failed to connect when logging in with authelia #296

New issue

Open

opened 2025-10-14 16:14:50 -06:00 by navan · 0 comments

navan commented

2025-10-14 16:14:50 -06:00

Owner

Originally created by @SamsiFPV on 6/12/2025

What happened?

When I am logging in with authelia, the notification pops up "Socket failed to connect".
If I log in with password, everything works.

The only differences I can see on those two requests is the authelia session cookie.

What did you expect to happen?

I expect the app to work with the authelia login

Steps to reproduce the issue

Log in with authelia
Website displays "Socket failed to connect" after a few seconds.

Audiobookshelf version

v2.24.0

How are you running audiobookshelf?

Other (list in "Additional Notes" box)

What OS is your Audiobookshelf server hosted from?

Other (list in "Additional Notes" box)

If the issue is being seen in the UI, what browsers are you seeing the problem on?

None

Logs

Additional Notes

abs is running on truenas, accessed via a reverse proxy made with nginx.

*Originally created by @SamsiFPV on 6/12/2025* ### What happened? When I am logging in with authelia, the notification pops up "Socket failed to connect". If I log in with password, everything works. The only differences I can see on those two requests is the authelia session cookie. ### What did you expect to happen? I expect the app to work with the authelia login ### Steps to reproduce the issue 1. Log in with authelia 2. Website displays "Socket failed to connect" after a few seconds. ### Audiobookshelf version v2.24.0 ### How are you running audiobookshelf? Other (list in "Additional Notes" box) ### What OS is your Audiobookshelf server hosted from? Other (list in "Additional Notes" box) ### If the issue is being seen in the UI, what browsers are you seeing the problem on? None ### Logs ```shell ``` ### Additional Notes abs is running on truenas, accessed via a reverse proxy made with nginx.