[Bug]: Multiple issues on IOS side with streaming #1974

New issue

Closed

opened 2026-02-20 10:14:30 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-20 10:14:30 -05:00

Owner

Originally created by @johnruck on GitHub (May 9, 2024).

What happened?

These are all on IOS talking to a AudioBookShelf server behind a nginx proxy manager front end (with the websockets selection active) using https. All issues are also when connected to the local network.

Talking to the website with just Safari (started from a safari opening session) works for streaming, but for some reason even while it is working the big red banner saying that websocket is not connected.
Attempting to "Add to Home Screen" the main AudioBookShelf page results in a dead app that doesnt load at all.
Using the iOS App available in TestFlight is unable to stream at all, even when it shows the green socket connection, Downloads work fine. And yes I already tried the completely uninstall and reinstall of the app this morning.

So I have a workaround via #1 above to get streaming working again, but figured I should report the behavior I am seeing on #2 and #3 to see if those pathways can be resolved. (#3 would be my idea way of operating).

Your readme.md is also a little unclear of whether the configuration you show in the NGINX reverse proxy section need to be applied when using Nginx Proxy Manager as well - at this time I only have the Nginx Proxy Manager configuration active.

What did you expect to happen?

I expected streaming to work in all of the above scenarios.

Steps to reproduce the issue

Audiobookshelf version

Docker 2.8.1

How are you running audiobookshelf?

Docker

What OS is your Audiobookshelf server hosted from?

Linux

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

None

Logs

No response

Additional Notes

No response

Originally created by @johnruck on GitHub (May 9, 2024). ### What happened? These are all on IOS talking to a AudioBookShelf server behind a nginx proxy manager front end (with the websockets selection active) using https. All issues are also when connected to the local network. 1. Talking to the website with just Safari (started from a safari opening session) works for streaming, but for some reason even while it is working the big red banner saying that websocket is not connected. 2. Attempting to "Add to Home Screen" the main AudioBookShelf page results in a dead app that doesnt load at all. 3. Using the iOS App available in TestFlight is unable to stream at all, even when it shows the green socket connection, Downloads work fine. And yes I already tried the completely uninstall and reinstall of the app this morning. So I have a workaround via #1 above to get streaming working again, but figured I should report the behavior I am seeing on #2 and #3 to see if those pathways can be resolved. (#3 would be my idea way of operating). Your readme.md is also a little unclear of whether the configuration you show in the NGINX reverse proxy section need to be applied when using Nginx Proxy Manager as well - at this time I only have the Nginx Proxy Manager configuration active. ### What did you expect to happen? I expected streaming to work in all of the above scenarios. ### Steps to reproduce the issue 1. ### Audiobookshelf version Docker 2.8.1 ### How are you running audiobookshelf? Docker ### What OS is your Audiobookshelf server hosted from? Linux ### If the issue is being seen in the UI, what browsers are you seeing the problem on? None ### Logs _No response_ ### Additional Notes _No response_

deekerman

2026-02-20 10:14:30 -05:00

closed this issue
added the
bug
label

deekerman commented

2026-02-20 10:14:33 -05:00

Author

Owner

@johnruck commented on GitHub (May 9, 2024):

Realized I forgot to mention - all of this is on iOS 17.4.1

@johnruck commented on GitHub (May 9, 2024): Realized I forgot to mention - all of this is on iOS 17.4.1

deekerman commented

2026-02-20 10:14:33 -05:00

Author

Owner

@nichwall commented on GitHub (May 9, 2024):

The NGINX configuration is an example for NGINX, and the NPM is an example for NPM, so yes do not use the NGINX example for NPM.

Have you verified everything works when not using the reverse proxy and connecting directly by local IP/port (not going through the reverse proxy)?

It might be easier to get help with specific reverse proxy issues in the ABS Discord so a community member can help if your setup matches theirs.

@nichwall commented on GitHub (May 9, 2024): The NGINX configuration is an example for NGINX, and the NPM is an example for NPM, so yes do not use the NGINX example for NPM. Have you verified everything works when not using the reverse proxy and connecting directly by local IP/port (not going through the reverse proxy)? It might be easier to get help with specific reverse proxy issues in the ABS Discord so a community member can help if your setup matches theirs.