@advplyr commented on GitHub (May 15, 2025):
Here is some info. https://github.com/advplyr/audiobookshelf/issues/3868#issuecomment-2605327783
@Vito0912 commented on GitHub (May 15, 2025):
For anyone using Portainer (or ofc docker compose), this was resolved by accident when I tried the following with someone:
Add these lines to your…
@ykarus117 commented on GitHub (May 15, 2025):
Last time this came up with Synology someone broke down exactly why this happens. It is a Synology bug with container caching or something like…
@github-actions[bot] commented on GitHub (Aug 26, 2025):
Fixed in v2.29.0.
@Vito0912 commented on GitHub (May 15, 2025):
Duplicate of https://github.com/advplyr/audiobookshelf/issues/4289
@Kapot commented on GitHub (May 15, 2025):
This is marked as a duplicate, but i'd like to add that the suggested solutions there dont seem to work for me.
- Using '2.20.0' instead of 'latest'…
@Vito0912 commented on GitHub (May 15, 2025):
Duplicate of https://github.com/advplyr/audiobookshelf/issues/1135
@magicboy2000 commented on GitHub (May 30, 2025):
Thank you very much, i will find the version related to #1135 request.
@Cotignac commented on GitHub (May 15, 2025):
I'm not familiar with how to downgrade. Never been forced to do that. Please let me know how to do it.
@Kapot commented on GitHub (May 15, 2025):
I'm not familiar with how to downgrade. Never been forced to do that. Please let me know how to do it.
Duplicate/Edit the container, but edit the…
@Vito0912 commented on GitHub (May 15, 2025):
This is marked as a duplicate, but i'd like to add that the suggested solutions there dont seem to work for me.
I also think that the original…
@Cotignac commented on GitHub (May 15, 2025):
I have to agree. I've tried to downgrade to version 2.21.0 and to 2.20.0 and none of them works.
@Vito0912 commented on GitHub (May 15, 2025):
One idea I have is to completely delete the container by running docker compose down and then docker compose up -d. Keep in mind that this will…
@ykarus117 commented on GitHub (May 15, 2025):
Same error with portainer after re-creating the container with latest image from 2.21.0
@mkstephenson commented on GitHub (May 15, 2025):
On Synology I was able to get it running after cleaning the project and rebuilding (I am running it using docker compose in the container manager).
@advplyr commented on GitHub (May 15, 2025):
Last time this came up with Synology someone broke down exactly why this happens. It is a Synology bug with container caching or something like that,…