Root user login reset to default after server updates #48

Closed
opened 2026-04-24 22:57:09 +02:00 by adam · 12 comments
Owner

Originally created by @scorpio862 on GitHub (Oct 5, 2021).

I noticed that some updates of the AudioBookshelf server are causing the reset of the root user login details.
So my username goes back to Root but the bigger problem is that the password is beeing removed.

My server is accesible externally from the web so few times I ended up with unsecured access to the server so anybody could access it until I noticed this and set up the password again.

This happened after recent update to v1.3.5 and few times before.

Originally created by @scorpio862 on GitHub (Oct 5, 2021). I noticed that some updates of the AudioBookshelf server are causing the reset of the root user login details. So my username goes back to Root but the bigger problem is that the password is beeing removed. My server is accesible externally from the web so few times I ended up with unsecured access to the server so anybody could access it until I noticed this and set up the password again. This happened after recent update to v1.3.5 and few times before.
adam closed this issue 2026-04-24 22:57:09 +02:00
Author
Owner

@advplyr commented on GitHub (Oct 6, 2021):

I just released an update v1.4.0.
When you get a moment can you update and see if the user gets reset again?

@advplyr commented on GitHub (Oct 6, 2021): I just released an update `v1.4.0`. When you get a moment can you update and see if the user gets reset again?
Author
Owner

@scorpio862 commented on GitHub (Oct 6, 2021):

I just updated to 1.4.0 and there was no root user reset.
I'm following this project since it appeared in Unraid comunity apps and I noticed user reset maybe around 4 times so it wasn't after every single update. It looks like only the root user was reset. The other users I've created has were fine.

@scorpio862 commented on GitHub (Oct 6, 2021): I just updated to 1.4.0 and there was no root user reset. I'm following this project since it appeared in Unraid comunity apps and I noticed user reset maybe around 4 times so it wasn't after every single update. It looks like only the root user was reset. The other users I've created has were fine.
Author
Owner

@scorpio862 commented on GitHub (Oct 11, 2021):

Update to v1.4.4 has just reset the root login details to default again

@scorpio862 commented on GitHub (Oct 11, 2021): Update to v1.4.4 has just reset the root login details to default again
Author
Owner

@advplyr commented on GitHub (Oct 11, 2021):

Can you check the logs for any errors on startup?

@advplyr commented on GitHub (Oct 11, 2021): Can you check the logs for any errors on startup?
Author
Owner

@scorpio862 commented on GitHub (Oct 11, 2021):

The AudioBooshelf logger page does not show any logs from the strartup so I didn't see any errors. It looks like it starts showing the logs from the moment I open logger page and set it to Debug. Maybe adding option to save Logs to file would help.

I checked the container log as well and there was no errors in the log.

I just updated to v.1.4.5 and the root accound didn't reset to default after this update.

@scorpio862 commented on GitHub (Oct 11, 2021): The AudioBooshelf logger page does not show any logs from the strartup so I didn't see any errors. It looks like it starts showing the logs from the moment I open logger page and set it to Debug. Maybe adding option to save Logs to file would help. I checked the container log as well and there was no errors in the log. I just updated to v.1.4.5 and the root accound didn't reset to default after this update.
Author
Owner

@advplyr commented on GitHub (Oct 11, 2021):

Ugh, this is a tough one. I will come up with a temporary solution so that users aren't leaving their servers unsecured, but still need to track this one down.

@advplyr commented on GitHub (Oct 11, 2021): Ugh, this is a tough one. I will come up with a temporary solution so that users aren't leaving their servers unsecured, but still need to track this one down.
Author
Owner

@scorpio862 commented on GitHub (Oct 16, 2021):

It happened again with the latest update v1.4.9 :)
The root login got reset to default with no password.

@scorpio862 commented on GitHub (Oct 16, 2021): It happened again with the latest update v1.4.9 :) The root login got reset to default with no password.
Author
Owner

@advplyr commented on GitHub (Oct 16, 2021):

Do you have other users, and those users are not getting reset? Just the root?

@advplyr commented on GitHub (Oct 16, 2021): Do you have other users, and those users are not getting reset? Just the root?
Author
Owner

@scorpio862 commented on GitHub (Oct 16, 2021):

I have another user and it never changes. Only the root user gets reset to default.

@scorpio862 commented on GitHub (Oct 16, 2021): I have another user and it never changes. Only the root user gets reset to default.
Author
Owner

@advplyr commented on GitHub (Oct 16, 2021):

I just pushed a patch if you can update when you get a chance and check the first few logs that should look like this:
You'll have to check the log from the container still

[2021-10-16T12:47:38.621Z] INFO: === Starting Server ===
[2021-10-16T12:47:38.621Z] INFO: [Server] Init v1.4.9
[2021-10-16T12:47:38.677Z] INFO: [DB] 2 Libraries Loaded
[2021-10-16T12:47:38.677Z] INFO: [DB] 3 Users Loaded
[2021-10-16T12:47:38.743Z] INFO: [DB] 121 Audiobooks Loaded
[2021-10-16T12:47:38.744Z] INFO: [Db] Root user exists, pw: true

Last line checks if the root user has a password.
If the root user is not found then that last log line will instead be

[2021-10-16T12:47:38.744Z] INFO: [Db] Root user created
@advplyr commented on GitHub (Oct 16, 2021): I just pushed a patch if you can update when you get a chance and check the first few logs that should look like this: You'll have to check the log from the container still ```bash [2021-10-16T12:47:38.621Z] INFO: === Starting Server === [2021-10-16T12:47:38.621Z] INFO: [Server] Init v1.4.9 [2021-10-16T12:47:38.677Z] INFO: [DB] 2 Libraries Loaded [2021-10-16T12:47:38.677Z] INFO: [DB] 3 Users Loaded [2021-10-16T12:47:38.743Z] INFO: [DB] 121 Audiobooks Loaded [2021-10-16T12:47:38.744Z] INFO: [Db] Root user exists, pw: true ``` Last line checks if the root user has a password. If the root user is not found then that last log line will instead be ```bash [2021-10-16T12:47:38.744Z] INFO: [Db] Root user created ```
Author
Owner

@scorpio862 commented on GitHub (Oct 16, 2021):

I just updated the server and the log looks good.

[2021-10-16T13:39:29.950Z] INFO: === Starting Server ===
[2021-10-16T13:39:29.950Z] INFO: [Server] Init v1.4.9
[2021-10-16T13:39:29.986Z] INFO: [DB] 1 Libraries Loaded
[2021-10-16T13:39:29.986Z] DEBUG: Set Log Level to DEBUG
[2021-10-16T13:39:29.987Z] INFO: [DB] 2 Users Loaded
[2021-10-16T13:39:30.021Z] INFO: [DB] 58 Audiobooks Loaded
[2021-10-16T13:39:30.021Z] INFO: [Db] Root user exists, pw: true

I'll be checking this log every time I update the server and maybe if the root user gets reset to default again, I will see it in the logs.
I renemed the root user so I hope this doesn't cause the problems.

@scorpio862 commented on GitHub (Oct 16, 2021): I just updated the server and the log looks good. > [2021-10-16T13:39:29.950Z] INFO: === Starting Server === [2021-10-16T13:39:29.950Z] INFO: [Server] Init v1.4.9 [2021-10-16T13:39:29.986Z] INFO: [DB] 1 Libraries Loaded [2021-10-16T13:39:29.986Z] DEBUG: Set Log Level to DEBUG [2021-10-16T13:39:29.987Z] INFO: [DB] 2 Users Loaded [2021-10-16T13:39:30.021Z] INFO: [DB] 58 Audiobooks Loaded [2021-10-16T13:39:30.021Z] INFO: [Db] Root user exists, pw: true I'll be checking this log every time I update the server and maybe if the root user gets reset to default again, I will see it in the logs. I renemed the root user so I hope this doesn't cause the problems.
Author
Owner

@advplyr commented on GitHub (Oct 28, 2021):

This just happened to me... and I lost all my audiobook progress on root.
Luckily I had daily backups turned on so I only lost todays progress.

I'm pretty sure now that it is the database, so I will be taking steps to resolve this.

Update: I just realized that I was streaming an audiobook while I restarted the docker image. I'm guessing that has something to do with it.

@advplyr commented on GitHub (Oct 28, 2021): This just happened to me... and I lost all my audiobook progress on root. Luckily I had daily backups turned on so I only lost todays progress. I'm pretty sure now that it is the database, so I will be taking steps to resolve this. Update: I just realized that I was streaming an audiobook while I restarted the docker image. I'm guessing that has something to do with it.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/audiobookshelf#48