[Bug]: Socket failed to connect #1446

Closed
opened 2026-04-24 23:45:48 +02:00 by adam · 5 comments
Owner

Originally created by @arinrare on GitHub (Oct 7, 2023).

Describe the issue

QNAP qpkg version 2.4.4.0 x86_64
Accessing via http locally
Fresh install

Was able to install, create user, select media folder, scan for files.
Then on going to the library to view audibooks get a repeated socket failed to connect error.
This is what is showing in the browser dev window:

image

Tried restarting the service, same error on going back in to library.

Steps to reproduce the issue

  1. Install QNAP package
  2. Create a user and login
  3. Add a media folder
  4. Scan library
  5. Attempt to view library via web interface on http

Audiobookshelf version

2.4.4.0x86_64 from QNAP store

How are you running audiobookshelf?

Other

Originally created by @arinrare on GitHub (Oct 7, 2023). ### Describe the issue QNAP qpkg version 2.4.4.0 x86_64 Accessing via http locally Fresh install Was able to install, create user, select media folder, scan for files. Then on going to the library to view audibooks get a repeated socket failed to connect error. This is what is showing in the browser dev window: ![image](https://github.com/advplyr/audiobookshelf/assets/5018715/9ffb619d-c11d-42e8-ba90-6a0d484c25b0) Tried restarting the service, same error on going back in to library. ### Steps to reproduce the issue 1. Install QNAP package 2. Create a user and login 3. Add a media folder 4. Scan library 5. Attempt to view library via web interface on http ### Audiobookshelf version 2.4.4.0x86_64 from QNAP store ### How are you running audiobookshelf? Other
adam added the bug label 2026-04-24 23:45:48 +02:00
adam closed this issue 2026-04-24 23:45:49 +02:00
Author
Owner

@advplyr commented on GitHub (Oct 7, 2023):

The QNAP package isn't maintained by anyone associated with this project. Abs needs to be able to establish a socket connection so I think you should raise this issue with the QNAP package maintainer

@advplyr commented on GitHub (Oct 7, 2023): The QNAP package isn't maintained by anyone associated with this project. Abs needs to be able to establish a socket connection so I think you should raise this issue with the QNAP package maintainer
Author
Owner

@advplyr commented on GitHub (Oct 7, 2023):

Also, feel free to join the discord or matrix server. Someone may be able to help you there

@advplyr commented on GitHub (Oct 7, 2023): Also, feel free to join the discord or matrix server. Someone may be able to help you there
Author
Owner

@arinrare commented on GitHub (Oct 7, 2023):

Ok thank you.

@arinrare commented on GitHub (Oct 7, 2023): Ok thank you.
Author
Owner

@arinrare commented on GitHub (Oct 7, 2023):

For any other QNAP user who comes across this bug, just install with Container Station, very easy to set up and works without issue

@arinrare commented on GitHub (Oct 7, 2023): For any other QNAP user who comes across this bug, just install with Container Station, very easy to set up and works without issue
Author
Owner

@y2ksw commented on GitHub (Sep 1, 2024):

I had this issue on a Plesk server and not in local. So I went manually to the /var/www/vhosts/system folder to the respective domain and edited the docker entry on nginx.conf with the following additions (see ADD THIS). That solved it.

        #extension docker begin
        location ~ ^/.* {
                proxy_pass http://0.0.0.0:13378;
                proxy_set_header Host              $host;
                proxy_set_header X-Real-IP         $remote_addr;
                proxy_set_header X-Forwarded-For   $proxy_add_x_forwarded_for;
                proxy_set_header X-Forwarded-Proto $scheme;
                # ADD THIS:
                proxy_set_header Upgrade            $http_upgrade;
                proxy_set_header Connection         "upgrade";
                proxy_http_version                  1.1;
                proxy_redirect                      http:// https://;
        }

        #extension docker end
@y2ksw commented on GitHub (Sep 1, 2024): I had this issue on a Plesk server and not in local. So I went manually to the /var/www/vhosts/system folder to the respective domain and edited the docker entry on nginx.conf with the following additions (see **ADD THIS**). That solved it. ``` #extension docker begin location ~ ^/.* { proxy_pass http://0.0.0.0:13378; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; # ADD THIS: proxy_set_header Upgrade $http_upgrade; proxy_set_header Connection "upgrade"; proxy_http_version 1.1; proxy_redirect http:// https://; } #extension docker end ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#1446