[Bug]: Issues after re-installing Audiobookshelf #2793

Closed
opened 2026-04-25 00:10:43 +02:00 by adam · 6 comments
Owner

Originally created by @oboe45 on GitHub (May 23, 2025).

What happened?

After some issues following a recent storm, I had to replace several drives on my NAS which houses Audiobookshelf and around 2200 .m4b audio books. This is a Synology DS9920+ server running DSM 7.2.2-72806 Update 3 - it has been running well for couple of years, with periodic updates to software as needed. I reinstalled everything, including Container Manager, with Portainer and Audiobook shelf, then I reloaded all of my .m4b books (which took around 15 hours) from backup storage. I ran the Audiobookshelf app under Mac OS/ Safari, and most things seem to work OK except noted below:

What did you expect to happen?

  1. Container Manager says that AUdiobookshelf has an issue: When I look at the CM display for Audiobookshelf, the heading line says: - in orange text : /bin/sh: curl: not found. - I have no idea what this means, nor how to fix it.
  2. ABS loads and all 2,170 books are displayed, with titles, cover pictures, Author and reader names and descriptive text. Any of the books can be selected and played, but some minor issues; first I cannot find any way to update the Author items to show Author names and descriptions for the books for each author - the authors are listed with a picture block, but I cannot find a way to add the pictures and short bio - these used to show up automatically on the lost version of this app. Second, there seems to be no way to associate a book with a series. This used to be automatic for me.

Almost everything works, but I cannot see how to get everything to work! What am I missing??

Steps to reproduce the issue

Crash the system, replace all hard disks and reinstall everything from scratch!

Audiobookshelf version

V2.23.0

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?

Safari

Logs


Additional Notes

No response

Originally created by @oboe45 on GitHub (May 23, 2025). ### What happened? After some issues following a recent storm, I had to replace several drives on my NAS which houses Audiobookshelf and around 2200 .m4b audio books. This is a Synology DS9920+ server running DSM 7.2.2-72806 Update 3 - it has been running well for couple of years, with periodic updates to software as needed. I reinstalled everything, including Container Manager, with Portainer and Audiobook shelf, then I reloaded all of my .m4b books (which took around 15 hours) from backup storage. I ran the Audiobookshelf app under Mac OS/ Safari, and most things seem to work OK except noted below: ### What did you expect to happen? 1. Container Manager says that AUdiobookshelf has an issue: When I look at the CM display for Audiobookshelf, the heading line says: - in orange text : /bin/sh: curl: not found. - I have no idea what this means, nor how to fix it. 2. ABS loads and all 2,170 books are displayed, with titles, cover pictures, Author and reader names and descriptive text. Any of the books can be selected and played, but some minor issues; first I cannot find any way to update the Author items to show Author names and descriptions for the books for each author - the authors are listed with a picture block, but I cannot find a way to add the pictures and short bio - these used to show up automatically on the lost version of this app. Second, there seems to be no way to associate a book with a series. This used to be automatic for me. Almost everything works, but I cannot see how to get everything to work! What am I missing?? ### Steps to reproduce the issue Crash the system, replace all hard disks and reinstall everything from scratch! ### Audiobookshelf version V2.23.0 ### 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? Safari ### Logs ```shell ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:10:43 +02:00
adam closed this issue 2026-04-25 00:10:43 +02:00
Author
Owner

@nichwall commented on GitHub (May 23, 2025):

Duplicate of https://github.com/advplyr/audiobookshelf/issues/4292

The audiobookshelf container no longer includes curl because it is not (and has not really ever been) used by the Audiobookshelf server. If you are just using curl as a healthcheck with no external monitoring there is not really a point to have the health check because the container will restart itself anyway if the server crashes. See more information in this comment: https://github.com/advplyr/audiobookshelf/issues/4292#issuecomment-2884326993

@nichwall commented on GitHub (May 23, 2025): Duplicate of https://github.com/advplyr/audiobookshelf/issues/4292 The audiobookshelf container no longer includes curl because it is not (and has not really ever been) used by the Audiobookshelf server. If you are just using curl as a healthcheck with no external monitoring there is not really a point to have the health check because the container will restart itself anyway if the server crashes. See more information in this comment: https://github.com/advplyr/audiobookshelf/issues/4292#issuecomment-2884326993
Author
Owner

@aHawtPotato commented on GitHub (May 31, 2025):

I was encountering the same issue. This issue is the compose script, and a coincidence that it happened after your power outage. It seems the audiobookshelf container has changed a bit and your compose no longer works perfectly with it.

https://mariushosting.com/how-to-install-audiobookshelf-on-your-synology-nas/

Assuming you used this guide initially, it looks the same but its changed a bit. The built in health check in the script has different code. Look at the script and compare to your setup.

The old health check refers to CURL, the new one does not. Id have shown the comparison but already deleted my old setup.

Good luck!

@aHawtPotato commented on GitHub (May 31, 2025): I was encountering the same issue. This issue is the compose script, and a coincidence that it happened after your power outage. It seems the audiobookshelf container has changed a bit and your compose no longer works perfectly with it. https://mariushosting.com/how-to-install-audiobookshelf-on-your-synology-nas/ Assuming you used this guide initially, it looks the same but its changed a bit. The built in health check in the script has different code. Look at the script and compare to your setup. The old health check refers to CURL, the new one does not. Id have shown the comparison but already deleted my old setup. Good luck!
Author
Owner

@oboe45 commented on GitHub (May 31, 2025):

Thanks, but does this mean a complete reinstall including the input of the 2000 audiobooks?

@oboe45 commented on GitHub (May 31, 2025): Thanks, but does this mean a complete reinstall including the input of the 2000 audiobooks?
Author
Owner

@aHawtPotato commented on GitHub (May 31, 2025):

Thanks, but does this mean a complete reinstall including the input of the 2000 audiobooks?

Oof, that's a scary thought, but you're in luck.

Not at all!
Just make the changes in the docker/container manager/portainer editor (or your yml file, depending on how you installed it).
You can have it repull/update the image if needed (not a bad thing to do) but all your settings and data will remain the same (assuming you don't do something weird 😜)!

How'd you do your install? Portainer? Container manager? I can walk you through it if needed.

(Note: this may not fix your artwork, it sounds like you may need to run a metadata check again - that's done through audiobookshelf settings/can be done individually for each book which sound...like a lot... For your library)

Settings > set your preferred scanner settings

Settings > library > '...' > match books

  • let it run for a while
@aHawtPotato commented on GitHub (May 31, 2025): - [ ] > Thanks, but does this mean a complete reinstall including the input of the 2000 audiobooks? Oof, that's a scary thought, but you're in luck. Not at all! Just make the changes in the docker/container manager/portainer editor (or your yml file, depending on how you installed it). You can have it repull/update the image if needed (not a bad thing to do) but all your settings and data will remain the same (assuming you don't do something weird 😜)! How'd you do your install? Portainer? Container manager? I can walk you through it if needed. (Note: this may not fix your artwork, it sounds like you may need to run a metadata check again - that's done through audiobookshelf settings/can be done individually for each book which sound...like a lot... For your library) Settings > set your preferred scanner settings Settings > library > '...' > match books - let it run for a while
Author
Owner

@DaBear78 commented on GitHub (Jun 4, 2025):

Can you please explain how to make the changes? I used the mariushosting guide to install it (the old one), but I don't know how to change the config to make the error go away. If it helps: I have portainer installed.

@DaBear78 commented on GitHub (Jun 4, 2025): Can you please explain how to make the changes? I used the mariushosting guide to install it (the old one), but I don't know how to change the config to make the error go away. If it helps: I have portainer installed.
Author
Owner

@aHawtPotato commented on GitHub (Jun 26, 2025):

Can you please explain how to make the changes? I used the mariushosting guide to install it (the old one), but I don't know how to change the config to make the error go away. If it helps: I have portainer installed.

Try to refollow the guide. It looks very similar but there are slight changes that will fix your issue.

Lmk if you're still stuck.

@aHawtPotato commented on GitHub (Jun 26, 2025): > Can you please explain how to make the changes? I used the mariushosting guide to install it (the old one), but I don't know how to change the config to make the error go away. If it helps: I have portainer installed. Try to refollow the guide. It looks very similar but there are slight changes that will fix your issue. Lmk if you're still stuck.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#2793