Replies: 2 comments 3 replies
-
When I did this I had to add the user credentials using filebrowser command line interface because the default install didn't have any users installed by default (possibly because I was initially trying to use noauth). When the session timed out after two hours (the default) it presented me with a login screen but no users were established, so I was locked out. This may have been just the wonky way I initially tried to set this up, and perhaps you stumbled on that method as well. If all else fails, do a "filebrowser config init" to zero-out any unintended foolishness and see if that restores the default admin user. If that's still a problem, "filebrowser users add " should at least establish a default user-level account you can get into, and a "filebrowser users update --perm.admin" should be the correct syntax to make that user an admin. From there, the settings menu should help you get most of the rest of the setup you need done. Hope this helps. |
Beta Was this translation helpful? Give feedback.
-
When it comes time to establish filebrowser as a systemd service that will start on boot, here's what I did: New file: /etc/systemd/service/filebrowser.service
setup commands:
|
Beta Was this translation helpful? Give feedback.
-
Just installed Filebrowser on my Raspberry 4b using the built in software installation menu, it seemed to install without error and I can open the Filebrowser web interface and see the login page, but I can't log in with the default usename and password admin and admin, or admin and admin123, it says "wrong credentials" can anyone help me with this.
Beta Was this translation helpful? Give feedback.
All reactions