Socket failed to connect

[dietrichmd]

Fresh install using docker-compose and apache2. I can access site and login, but everything I try to do is greeted with a Socket Failed to Connect error.

Please advise.

Thanks

[dietrichmd]

here is proxypass info

ProxyPreserveHost On
ProxyPass /.well-known/ !
ProxyPass / http://192.168.1.11:4040/
ProxyPassReverse /.well-known/ !
ProxyPassReverse / http://192.168.1.11:4040/
Alias / http://192.168.1.11:4040/
RewriteEngine on
RewriteCond %{HTTP:Upgrade} websocket [NC]
RewriteCond %{HTTP:Connection} upgrade [NC]
RewriteRule ^/?(.*) "ws://localhost:4040/$1" [P,L]

[dietrichmd]

Solved: proxy_wstunnel_module was not enabled. For those looking, its a2enmod proxy_wstunnel

[silentArtifact]

I'm having this issue, but only when attempting to stream off the local network. Everything else works. It's running from Docker on a Synology NAS.

[advplyr]

Running a reverse proxy? SSL?

[silentArtifact]

Yeah, reverse proxy set up through the DMS os itself, same with SSL. I've got the same thing done with Plex and a bunch of other containers, so I'm not sure what I should do with this.

[timbatog]

I have they same issue with NGiNX 11 Feb 2022, 15:21 by ***@***.***:

…

Yeah, reverse proxy set up through the DMS os itself, same with SSL. I've got the same thing done with Plex and a bunch of other containers, so I'm not sure what I should do with this. — Reply to this email directly, > view it on GitHub <#241 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7CETTI4BQU7OZ6YDDZQHLU2USPFANCNFSM5KA4T4GQ>> . Triage notifications on the go with GitHub Mobile for > iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>> or > Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>> . You are receiving this because you are subscribed to this thread.> Message ID: > <advplyr/audiobookshelf/issues/241/1036325660> @> github> .> com>

[advplyr]

The difference is that audiobookshelf requires a web socket connection, so the reverse proxy config will probably not be the exact same as other media servers. In NGINX proxy manager there is a toggle for web sockets support.

[timbatog]

You did it! thank you!! (this needs to be on a sticky somewhere - it's so helpful) 11 Feb 2022, 22:26 by ***@***.***:

…

The difference is that audiobookshelf requires a web socket connection, so the reverse proxy config will probably not be the exact same as other media servers. In NGINX proxy manager there is a toggle for web sockets support. <https://user-images.githubusercontent.com/67830747/153679106-b2a7f5b9-0702-48c6-9740-b26b401986e9.png> — Reply to this email directly, > view it on GitHub <#241 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7CETXMXVGXIXYN4O3U46TU2WEK5ANCNFSM5KA4T4GQ>> . Triage notifications on the go with GitHub Mobile for > iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>> or > Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>> . You are receiving this because you commented.> Message ID: > <advplyr/audiobookshelf/issues/241/1036688673> @> github> .> com>

[silentArtifact]

Agreed. For synology, I followed these steps:

1. Open Control Panel > Application Portal
2. Change to the Reverse Proxy tab
3. Select the proxy rule for which you want to enable Websockets and click on Edit
4. Change to the "Custom Header" tab
5. Click Create > WebSocket
6. Click Save

Now it works!

[advplyr]

Awesome, thanks for following up with your steps. It is still a bit messy, but I added your steps for synology and the screenshot for nginx proxy manager in the readme.
https://github.com/advplyr/audiobookshelf/blob/master/readme.md#reverse-proxy-set-up

[silentArtifact]

Hey, I should be thanking you for all the work you've done on this! It's exactly what I've been looking for, and I seriously appreciate all your effort!

[timbatog]

Agreed. This is excellent work! Can I donate? 11 Feb 2022, 23:23 by ***@***.***:

…

Hey, I should be thanking > you> for all the work you've done on this! It's exactly what I've been looking for, and I seriously appreciate all your effort! — Reply to this email directly, > view it on GitHub <#241 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7CETSE6CIUN6TQKNY6WVLU2WK6VANCNFSM5KA4T4GQ>> . Triage notifications on the go with GitHub Mobile for > iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>> or > Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>> . You are receiving this because you commented.> Message ID: > <advplyr/audiobookshelf/issues/241/1036751994> @> github> .> com>

[advplyr]

There is nothing setup for donations at the moment, but I appreciate your support!

[timbatog]

Pick a charity maybe? I’ll donate :) 12 Feb 2022, 00:07 by ***@***.***:

…

There is nothing setup for donations at the moment, but I appreciate your support! — Reply to this email directly, > view it on GitHub <#241 (comment)>> , or > unsubscribe <https://github.com/notifications/unsubscribe-auth/AF7CETQ4WBSSUVHXGE4PBQLU2WQEXANCNFSM5KA4T4GQ>> . Triage notifications on the go with GitHub Mobile for > iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675>> or > Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>> . You are receiving this because you commented.> Message ID: > <advplyr/audiobookshelf/issues/241/1036815054> @> github> .> com>

[advplyr]

Too much pressure! If you follow the project and donate when that need arrives then that would be ideal.

[PoepieFloepie]

Agreed. For synology, I followed these steps:

1. Open Control Panel > Application Portal

2. Change to the Reverse Proxy tab

3. Select the proxy rule for which you want to enable Websockets and click on Edit

4. Change to the "Custom Header" tab

5. Click Create > WebSocket

6. Click Save

Now it works!

Not working for https,if I do this for the ios app,only http is working ( that I don't want for outside my network)

[adamk33n3r]

Agreed. For synology, I followed these steps:

1. Open Control Panel > Application Portal
2. Change to the Reverse Proxy tab
3. Select the proxy rule for which you want to enable Websockets and click on Edit
4. Change to the "Custom Header" tab
5. Click Create > WebSocket
6. Click Save

Now it works!

Not working for https,if I do this for the ios app,only http is working ( that I don't want for outside my network)

Same, I'm trying to use https through reverse proxy (so the app still receives via http) and in the Android app it fails to ping and replaces what I've typed with http. It works fine if I connect from http but obviously I'd prefer to use https for everything.

Edit: I take it back that "it works fine". It does go to the login screen, but I am getting "Unknown error" when I try to log in.

[SyndicatedPillbug]

Agreed. For synology, I followed these steps:

1. Open Control Panel > Application Portal
2. Change to the Reverse Proxy tab
3. Select the proxy rule for which you want to enable Websockets and click on Edit
4. Change to the "Custom Header" tab
5. Click Create > WebSocket
6. Click Save

Now it works!

I'm missing the other information for this, though! What ports do I need to use? It's like the first half of the instructions are missing for this reverse proxy thing.

[onthecliff]

Agreed. For synology, I followed these steps:

1. Open Control Panel > Application Portal

2. Change to the Reverse Proxy tab

3. Select the proxy rule for which you want to enable Websockets and click on Edit

4. Change to the "Custom Header" tab

5. Click Create > WebSocket

6. Click Save

Now it works!

Thank you this worked immediately!

[coracoo]

great ,It work .

[guhanmathi]

The difference is that audiobookshelf requires a web socket connection, so the reverse proxy config will probably not be the exact same as other media servers. In NGINX proxy manager there is a toggle for web sockets support.

This helped in fixing my service showing socket errors running through nginx

[m4tz3]

DSM Changed a bit. could somebody share some screenshots with me? it's still not running at all for me

[robinjoseph08]

For posterity, just wanted to recount my experience here too, in case it helps someone else. I'm using a Synology NAS with DSM 7.2. I have ABS deployed using Container Manager, and it all works fine on my local network. I originally had ABS exposed publicly using Web Station (since that's also how I have Jellyfin exposed), but even though I could load it using my domain, it would always show the "Socket failed to connect" error.

Following these instructions, I deleted the entry for ABS in Web Station (since it doesn't seem like Web Station really has support for websockets yet) and instead went to the Reverse Proxy settings (now found in Control Panel > Login Portal > Advanced), and added entries for both HTTP and HTTPS for ABS, making sure to add the Websocket custom headers mentioned in this comment. After doing that, I was able to get ABS to connect to the socket without issue!

One thing I wanted to note though is that for some reason, if I try to access my domain when I'm on my local network, it's painfully slow, sometimes it times out, and the socket connection is very spotty. If I switch to just using the local IP of my NAS, everything is snappy and reliable again, and if I connect to the domain from a different network, it's also snappy. I mention this since it was messing up my testing a little bit because even after I fixed things with the Reverse Proxy settings, using my domain on my local network was still having issues, so I had to test it on a different network to see that it was fixed.

[rpgdev]

The difference is that audiobookshelf requires a web socket connection, so the reverse proxy config will probably not be the exact same as other media servers. In NGINX proxy manager there is a toggle for web sockets support.

This worked! Needed to wait a few minutes for the setting to take effect and audiobookshelf to tell me that it was able to connect the socket.

[loganank]

I had the same problem using typical nginx and not nginx proxy manager. Adding the following in the location portion of my .conf file fixed the issue, even when using ssl.

 location / {
        proxy_pass http://192.168.1.mylocalip:13378;
        proxy_http_version 1.1;
        proxy_set_header Upgrade $http_upgrade;
        proxy_set_header Connection 'upgrade';
        proxy_set_header Host $host;
        proxy_cache_bypass $http_upgrade;
        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;
    }

[kanine]

Thanks @loganank these were the lines that made the difference for me:

proxy_http_version 1.1;
proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection 'upgrade';
proxy_cache_bypass $http_upgrade;

[hjalte81]

The difference is that audiobookshelf requires a web socket connection, so the reverse proxy config will probably not be the exact same as other media servers. In NGINX proxy manager there is a toggle for web sockets support.

Thank you. That worked.