The latest update caused the docker container to stop running. I assume this is due to the recent changes mentioned above.

How can I fix this?

Using database: /db/database.db

open /db/database.db: permission denied

On 12/19/2024 at 5:08 PM, Tomahawk51 said:

Hello,  I'm looking for some input or help:  I'm finding that if I enter a Password, it doesn't stick after a docker update. What I find is that admin/admin is once again made available (making access to the service trivial).

 

This seems like a pretty big show stopper.  Here's what I've done: 

1. Delete everything, fresh install.

2. Install and use Docker defaults, add path to a test folder.  Login, change password (test with logout and it works). Restart container - works.

3. Choose to "force update (of docker)" in Unraid, go back to login - it's been reset. Admin/Admin works, but my changed password is not working.

Is anyone else able to confirm this, or that they don't see this issue? This makes me very uncomfortable trusting this moving forward without understanding this better.

Same thing! Any workaround?

On 6/29/2025 at 4:13 PM, kolofotias said:

Same thing! Any workaround?

the database is persistant but by default the config file (which contains the port filebrowser listens to) is not.

a real pain for me too. Had to disable auto-updates as I can't afford to have it update any time it wants and deprive me of accessing my files at a strategic time

On 6/23/2025 at 11:52 PM, Uderzo said:

The latest update caused the docker container to stop running. I assume this is due to the recent changes mentioned above.

How can I fix this?

A bit late I know but I had the same issue. Use the Settings > New permissions (not the "docker safe" one on the appdata share. It fixed the problem

On 6/29/2025 at 6:13 PM, kolofotias said:

Same thing! Any workaround?

For me, the issue was actually in the advanced view settings.

To fix a similar issue in the past, I had added " -- user 99:100" string to the Extra Parameters , but this time the fix was other way around. For whatever reason, the container did not want to start unless I actually emptied the "Extra Parameters" section, like so:



After this, worked like before.

Also I'd like to note, that running "New Permissions" as suggested above, could break permissions for other Docker containers. So use with care, or even better, go through the "shares" tab, navigate to AppData, and then change the permissions and owner for only the FileBrowser folder through there to not mess anything else up.

On 7/4/2025 at 3:08 PM, REllU said:

For me, the issue was actually in the advanced view settings.

To fix a similar issue in the past, I had added " -- user 99:100" string to the Extra Parameters , but this time the fix was other way around. For whatever reason, the container did not want to start unless I actually emptied the "Extra Parameters" section, like so:



After this, worked like before.

Also I'd like to note, that running "New Permissions" as suggested above, could break permissions for other Docker containers. So use with care, or even better, go through the "shares" tab, navigate to AppData, and then change the permissions and owner for only the FileBrowser folder through there to not mess anything else up.

If files require special permissions other than "nobody" user ownership, they have no business being in appdata. Mappings are there for that.

On 6/23/2025 at 5:38 PM, BurntOC said:

@knex666 Any chance you're tracking these latest changes?

Hey, I would love to find some time to do that - any idea how to get there quickly, than i´ll do that next weekend.

I have everything public in

https://github.com/maschhoff/docker/tree/master/filebrowser
https://github.com/maschhoff/docker/blob/master/unraid%20xml/my-filebrowser.xml

please feel free to maintain there, i´ll accept you pull request.

On 7/9/2025 at 10:19 PM, knex666 said:

Hey, I would love to find some time to do that - any idea how to get there quickly, than i´ll do that next weekend.

I have everything public in

https://github.com/maschhoff/docker/tree/master/filebrowser
https://github.com/maschhoff/docker/blob/master/unraid%20xml/my-filebrowser.xml

please feel free to maintain there, i´ll accept you pull request.

Hi

This is my first time making changes like this, so I wanted to mention that upfront. I followed the official changelog for File Browser v2.33.0 and updated both the JSON file (renamed it from filebrowser.json to settings.json) and the container XML template accordingly.

I also updated the descriptions and volume mappings to reflect the new structure—especially the database path (/database/filebrowser.db) and the need to keep config and database files in the same directory with correct ownership.

I’m not entirely sure how to properly test everything in a real-world setup, so I’d really appreciate it if someone could review the files before actually accepting or merging the changes. Just want to make sure I didn’t overlook anything.

Thanks a lot in advance!

So if I understand correctly, this docker every update defaults to admin and the log password and removes any user accounts created? That's what is happening to me at least.

3 minutes ago, NitroNine said:

So if I understand correctly, this docker every update defaults to admin and the log password and removes any user accounts created? That's what is happening to me at least.

the filebrowser got updated with a breaking change a while ago, you need to change your template

Edit: heres the link
https://github.com/filebrowser/filebrowser/releases/tag/v2.33.0

Edited August 9, 2025Aug 9 by Mainfrezzer

On 8/9/2025 at 1:13 PM, Mainfrezzer said:

the filebrowser got updated with a breaking change a while ago, you need to change your template

Edit: heres the link
https://github.com/filebrowser/filebrowser/releases/tag/v2.33.0

Thanks to @benjaminmue these updates are allready set to the Community Apps templates and files.
Grep that Template and see https://github.com/maschhoff/docker/tree/master/filebrowser for config files.

Edited August 17, 2025Aug 17 by knex666

On 6/29/2025 at 5:13 PM, kolofotias said:

Same thing! Any workaround?

I found the issue.

The path for the database inside the docker changed. For old versions the path was /db, the new path is /database.

So, the solution is to change the variable on the unraid docker's template:

Go here (ignore the 'do not change'):

Change it from this:

To this:

Now the bind mount will save everychange into the local unraid path /mnt/usr/appdata/filebrowser/db.

Maybe @knex666 can update the template so this could be a permanent fix.

Thank you.

Hello guys,

Total newbie here :-( .No knowledge of any kind in programing ….

I have installed and happily used Filebrowser since June. Two nights ago ,I have updated the Unraid and filebrowser….Since then I'm having one of the greatest headegs I ever had at frond of a computer.

Read everything I found , done everything I can and still the problem:

Ive managed to get the filebrowser work , but once I get to my files (pictures as example )I dont see them . If I try to download a file i get “unauthorized 401” ……cleared the permissions , deleted all the db, started from the beginning 100 times , but still no luck….

Please , HELP!

Nikolay

P.S.: once again total newbie

On 8/26/2025 at 6:25 PM, Juanzilla said:

I found the issue.

The path for the database inside the docker changed. For old versions the path was /db, the new path is /database.

So, the solution is to change the variable on the unraid docker's template:

Go here (ignore the 'do not change'):

Change it from this:

To this:

Now the bind mount will save everychange into the local unraid path /mnt/usr/appdata/filebrowser/db.

Maybe @knex666 can update the template so this could be a permanent fix.

Thank you.

Hey,

thanks to @benjaminmue the original Template is up to date, but you have your own copy once you install it.
You can run "reinstall" to download the latest template.

Or you'll find a copy on github.

https://github.com/maschhoff/docker/blob/master/unraid%20xml/my-filebrowser.xml

On 8/26/2025 at 1:25 PM, Juanzilla said:

I found the issue.

The path for the database inside the docker changed. For old versions the path was /db, the new path is /database.

So, the solution is to change the variable on the unraid docker's template:

Go here (ignore the 'do not change'):

Change it from this:

To this:

Now the bind mount will save everychange into the local unraid path /mnt/usr/appdata/filebrowser/db.

Maybe @knex666 can update the template so this could be a permanent fix.

Thank you.

Thank you a lot, this solved for me.

I try everything, even a chmod and permissions but I cant make persistent filebrowser since 2.33

every update it generate a new password and I havent a settings.json or database in the folder. I try unistall it and re-install but always the same. I try different folder names and the "db --> database" trick in the settings.

On 10/9/2025 at 7:07 AM, garion said:

I try everything, even a chmod and permissions but I cant make persistent filebrowser since 2.33

every update it generate a new password and I havent a settings.json or database in the folder. I try unistall it and re-install but always the same. I try different folder names and the "db --> database" trick in the settings.

SAME... ugh

On 8/26/2025 at 10:25 PM, Juanzilla said:

I found the issue.

The path for the database inside the docker changed. For old versions the path was /db, the new path is /database.

So, the solution is to change the variable on the unraid docker's template:

Go here (ignore the 'do not change'):

Change it from this:

To this:

Now the bind mount will save everychange into the local unraid path /mnt/usr/appdata/filebrowser/db.

Maybe @knex666 can update the template so this could be a permanent fix.

Thank you.

I have try it as your instruction but problem is filebrowser not started

I have try it as your following instruction but problem is filebrowser not started

For some reason I cannot get this docker app to stop listening on port 80. I've set the port in the WebUI section as well as the advanced view. I also set the networking to Bridged. Nothing I do will change the port.

Is this app still a thing?

Am I wasting my time on this? It seems to be abandonware.

Well this thing is just broke. Why is it even available?

Don't mean to beat a dead horse, but I assume this is just always going to be broken?

Every update clears all accounts made and you need to use the temp password to get into it?

WTH? I posted a response to this 2 days ago, but I don't see it now. Frustrating.

This works fine for me through upgrades. I'm busy at work but lemme hit the high points from my template (in addition to the standerd variables and such from the template):

Repository: filebrowser/filebrowser

Post arguments: -d /database/database.db

Path to database (path): container path /database host path /mnt/cache/appdata/filebrowser/db

Hope this helps.

After updating unraid and the docker I now don't have any thumbnails of the pictures anymore, I'm on 7.2.2 and Filebrowser is the "latest" version (2.49.0) as of 2025-11-24

hi ive been dealing with this issue for years and just getting annoyed

the container path is 80 but the host port i set is 8886

but everytime i click on the icon in docker to goto the webgui it always overwrites 8886 and just goes to port 80 and goes to the unraid page login.. is there a fix or something this been going on for years just i had enough of it doing this

you have to manually type it in

192.168.0.3:8886

Edited May 19May 19 by comet424