[Bug]: Lost my progress status after filestructure was changed #3056

Open
opened 2026-04-25 00:13:19 +02:00 by adam · 2 comments
Owner

Originally created by @Yur-ok on GitHub (Oct 27, 2025).

What happened?

I move my audiobooks folder to a new location.
After that I re-add my folder to the library.
And know whole library looks like new one!
All my progress and finished marks are gone!

Is there a way to return them back?

PS. I thought the progress depends on books / files name.

What did you expect to happen?

That all my progress status will save.

Steps to reproduce the issue

  1. move audiobooks folder to a new location
  2. go to library settings and remove old entry and add new one
  3. rescan library

Audiobookshelf version

2.30

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


Additional Notes

No response

Originally created by @Yur-ok on GitHub (Oct 27, 2025). ### What happened? I move my audiobooks folder to a new location. After that I re-add my folder to the library. And know whole library looks like new one! All my progress and finished marks are gone! Is there a way to return them back? PS. I thought the progress depends on books / files name. ### What did you expect to happen? That all my progress status will save. ### Steps to reproduce the issue 1. move audiobooks folder to a new location 2. go to library settings and remove old entry and add new one 3. rescan library ### Audiobookshelf version 2.30 ### 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 ```shell ``` ### Additional Notes _No response_
adam added the bug label 2026-04-25 00:13:19 +02:00
Author
Owner

@Vito0912 commented on GitHub (Oct 27, 2025):

This is not supported

@Vito0912 commented on GitHub (Oct 27, 2025): This is not supported
Author
Owner

@Vito0912 commented on GitHub (Oct 27, 2025):

While this is not supported, you say that you use Docker.
As long as the files internally do not change you should be able to load a backup.

Not supported are any changes to the file structure without ABS running or an disabled watcher. So you can move files, as long as your drive has support for inodes and ABS is running.

If you e.g. moved from native installment to docker it is not really possible to recover
In the upcoming docs (beta link, will not be available after pushed, so don't bookmark https://docs-beta.vito0912.de/docs/server-management/migration) there might be an unofficial way to move (see link above)

@Vito0912 commented on GitHub (Oct 27, 2025): While this is not supported, you say that you use Docker. As long as the files internally do not change you should be able to load a backup. Not supported are any changes to the file structure without ABS running or an disabled watcher. So you can move files, as long as your drive has support for inodes and ABS is running. If you e.g. moved from native installment to docker it is not really possible to recover In the upcoming docs (beta link, will not be available after pushed, so don't bookmark https://docs-beta.vito0912.de/docs/server-management/migration) there might be an unofficial way to move (see link above)
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#3056