@nichwall commented on GitHub (Feb 3, 2025):
If you are using Synology, make sure you are using the "Reset" method instead of the "Upgrade" button. https://github.com/advplyr/audiobookshelf/issues…
@mikelococo commented on GitHub (Jan 26, 2025):
For anyone looking to come up to speed on the history of this feature:
- [Design discussion](https://github.com/advplyr/audiobookshelf/discussions/…
@nichwall commented on GitHub (Jan 26, 2025):
Design discussion: Frustratingly, it appears that comments from sapd discussing why…
@Vito0912 commented on GitHub (Jan 21, 2025):
This is not an issue with ABS, but with the client (although maybe it would not be bad to limit the time that can be added to a open session at…
@jrhedman commented on GitHub (Jan 21, 2025):
@Dork74 Fun fact, if you ssh into your Synology and deploy via docker on the command line, you can still use the container manager interface once the…
@alternativesurfer commented on GitHub (Jan 21, 2025):
- Was this working for you on prior versions?
- Are you using a reverse proxy? If so, can you also replicate the issue with local ip…
@alternativesurfer commented on GitHub (Jan 24, 2025):
Something definitely changed, because previously there were no websocket issues when I used HAProxy (not Apache).
Now my console is filled…
@jstaubr commented on GitHub (Jan 31, 2025):
Older docker image did not have ENV "PORT=80". The new one I pulled has. Don't know where it came up with the port number 3333 though.
@niceguy4 commented on GitHub (Feb 3, 2025):
@20CCAA07 Thank you! Fixed my issue, too.
@advplyr commented on GitHub (Jan 21, 2025):
Thanks. Can you pull the image again and start a new container? And if Synology shows you the docker run command that it is using that would be the…
@Dork74 commented on GitHub (Jan 21, 2025):
Same as the Discord user, I duplicated and exported settings of the container, deleted original (after praying it wouldn't delete the database), then…
@advplyr commented on GitHub (Jan 21, 2025):
Thanks, it would be great to know how Synology is running the containers. Make sure you taking regular backups using the backup manager in Abs. So…
@jrhedman commented on GitHub (Jan 21, 2025):
Can confirm @Dork74's findings:
docker logs after simply duplicating the container and running the copy shows it's now listening on port 80:
@advplyr commented on GitHub (Jan 21, 2025):
Thanks for digging into it. It does seem to be something with caching although it wouldn't be the js file since that is in the container.
If someone…
@Dork74 commented on GitHub (Jan 21, 2025):
Have been running Abs (and a few other containers) for many months, including updates, with no problems. Not sure why Synology hated Abs this time. …