starred/audiobookshelf
1
0
Fork 0
mirror of https://github.com/advplyr/audiobookshelf.git synced 2026-05-30 23:40:40 +02:00
Code Issues 1.0k Packages Projects Releases 10 Wiki Activity

[Bug]: Socket Failed to Connect - Swag & Unraid #303

New Issue
Closed
opened 2026-04-24 23:04:09 +02:00 by adam · 1 comment
adam commented 2026-04-24 23:04:09 +02:00
Owner
Copy Link
Copy Source

Originally created by @Borlean on GitHub (Apr 26, 2022).

Describe the issue

UnRaid server using default community application template. When connecting locally via the IP address of my UnRaid server, everything works great.

However, once I try to go through my swag reverse proxy, with the below config from the readme, I am able to connect and login, but continually see a "Socket Failed to Connect" error. This happened on v2.0.1 and the new v2.0.2 version that was released a couple days ago.

  server {
    listen 443 ssl;
    listen [::]:443 ssl;
    
    server_name audiobookshelf.*;
    
    include /config/nginx/ssl.conf;

    location / {
      proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
      proxy_set_header Host $host;

      proxy_pass http://[IP of unRAID]:13378;

      proxy_http_version 1.1;
      proxy_set_header Upgrade $http_upgrade;
      proxy_set_header Connection "upgrade";
    }
  }

I saw there was another issue thread on 'Socket Failed to Connect' that was focused on nginx proxy manager (https://github.com/advplyr/audiobookshelf/issues/241#issuecomment-1036749487) and marked solved, but the socket error persists.

server {
  listen 443 ssl;
  listen [::]:443 ssl;

  server_name audiobookshelf.*;

  include /config/nginx/ssl.conf;

  location / {
    proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
    proxy_set_header X-Forwarded-Proto $scheme;
    proxy_set_header Host $host;
    proxy_set_header Upgrade $http_upgrade;
    proxy_set_header Connection "upgrade";

    proxy_http_version 1.1;

    proxy_pass http://[IP of unRAID]:13378;
    proxy_redirect http:// https://;

  }
}

Any ideas?

Steps to reproduce the issue

  1. Any login from outside the network through swag reverse proxy.

Audiobookshelf version

2.0.3

How are you running audiobookshelf?

Docker

edit: changed version from 2.0.2 to 2.0.3.

Originally created by @Borlean on GitHub (Apr 26, 2022). ### Describe the issue UnRaid server using default community application template. When connecting locally via the IP address of my UnRaid server, everything works great. However, once I try to go through my swag reverse proxy, with the below config from the readme, I am able to connect and login, but continually see a "Socket Failed to Connect" error. This happened on v2.0.1 and the new v2.0.2 version that was released a couple days ago. ``` server { listen 443 ssl; listen [::]:443 ssl; server_name audiobookshelf.*; include /config/nginx/ssl.conf; location / { proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header Host $host; proxy_pass http://[IP of unRAID]:13378; proxy_http_version 1.1; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; } } ``` I saw there was another issue thread on 'Socket Failed to Connect' that was focused on nginx proxy manager (https://github.com/advplyr/audiobookshelf/issues/241#issuecomment-1036749487) and marked solved, but the socket error persists. ``` server { listen 443 ssl; listen [::]:443 ssl; server_name audiobookshelf.*; include /config/nginx/ssl.conf; location / { proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header Host $host; proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; proxy_pass http://[IP of unRAID]:13378; proxy_redirect http:// https://; } } ``` Any ideas? ### Steps to reproduce the issue 1. Any login from outside the network through swag reverse proxy. ### Audiobookshelf version 2.0.3 ### How are you running audiobookshelf? Docker edit: changed version from 2.0.2 to 2.0.3.
adam added the bug label 2026-04-24 23:04:09 +02:00
adam closed this issue 2026-04-24 23:04:09 +02:00
adam commented 2026-04-24 23:04:10 +02:00
Author
Owner
Copy Link
Copy Source

@Borlean commented on GitHub (Apr 30, 2022):

Marking as closed. Adblocker/FB Container on Firefox was causing the issue. Disabling those and everything works.

@Borlean commented on GitHub (Apr 30, 2022): Marking as closed. Adblocker/FB Container on Firefox was causing the issue. Disabling those and everything works.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
authentication
backlog
bug
chapter editor
config-issue
ebooks
encoding/embedding
enhancement
help wanted
listening sessions & progress
planned
possible plugin
progress sync
pull-request
Mirrored from GitHub Pull Request
 sorting/filtering/searching
unable to reproduce
upload
users & permissions
waiting
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam (Adam Melkus)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#303
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?