I’ve re-installed 3 times and still have no password appear in the filebrowser container logs.
All I get is this…
2025-07-02 04:13:45.267856+00:002025/07/02 04:13:45 Using database: /config/filebrowser.db
2025-07-02 04:13:45.284228+00:002025/07/02 04:13:45 Using config file: /config/settings.json
2025-07-02 04:13:45.285815+00:002025/07/02 04:13:45 Listening on [::]:30051
I understand security and all, but why nanny people, just leave the admin:admin and i’ll change it.
Also, when ‘console’ was mentioned I opened up the web address and looked in Chrome console. Instructions are also very obtuse.
I hope they answer with a solution, I have and still have the same problem, no one would answer me, just answer the next dickhead which their before answer worked, so I’m paying attention to this thread
Well it all depends on who made the change. Was it the maintainer of the iX app or was it an upstream change from the file browser devs, like qbottorrent changed it a while back. If it’s upstream, there’s nothing iX can do about it.
I did find the randomly generated password at the top of the log file. At least it was there and it is 16 characters long. default minimum is 12 characters. The line looks like this:
2025/07/06 20:06:14 Randomly generated password for user 'admin': pjkfrgkBNgHFzYe1
This is just stupid to randomly generate a password then put it in plain text in a log file which does not increase security at all. I think it’s more a lets do something really dumb and see how many complain.
I’m already in the process of setting up the app not trying to hack my system so why not have places to set a default user and password (enforce a certain length and characters pw if desired) in the app setup,
or
set the user and password to the currently logged in admin user that is doing the setup,
or
set a default admin/admin and force a password reset on first login.
At least the file browser app actually recorded the password in the log, I ran across an app the other day that did not record the pw though it said to look in the log for it. That was really fun - not.
Good reddit thread on the same issue - /r/truenas/comments/1lfjbr1/whats_going_on_with_filebrowser/
I ran into the same issue. I had to delete the app and reinstall it a couple of times. The last time, i made sure to check the box for deleting the iXVolumes and Images. When I reinstalled it, this show up in my container logs and I was able to log in.
“2025-08-15 21:23:28.719574+00:002025/08/15 21:23:28 User ‘admin’ initialized with randomly generated password: V_V0f4tGoRjNIiiD”
I would have included screen shots but it won’t let me for some reason.
Hopefully this helps.
Cheers 
Disclaimer - I’m a complete novice with TrueNAS, this was a case of trial and error for me.
I tried this and it timed out for me and gave me an error
Are the TrueNAS-scale CE developers serious?
No inbuilt file browser in TrueNAS???!!!
RU kidding me?!
(P.S. the file browser “app” sucks- as is clearly demonstrated by this thread!)
Just MO!
I can’t be bothered with File Browser!
Can’t even easily view my own files direct on a brand new NAS (in 2025~!)
Can’t even login the first time!
What a complete and utter waste of time!
Just MO!
There is a file browser, it’s included in every install.
System → Shell
Use mc for the full experience, otherwise ls, cd and cat will get you far all on their own.
And activating ssh if you prefer is just a few clicks away, so is nfs and smb.
I ssh into the server often and use mc (Midnight Commander) all the time in Truenas. Nice handy file browser. For a GUI one I setup the File Browser app basic and it does work ok once setup, though mc is probably better. The file browser app is a royal pain because of the fact the password is in the first run log only. It used to have a anon user check mark setting in the setup that would open the file browser so at least you could set your own admin user and password but that seems to no longer be there. Third, is the fact it has to be configured for everything you wish to view.
On the user issue, I understand security hardening and all, but I think there should be a place to enter an admin user name and password during app setup, or since only an administrator should be in the back end of the server anyway, to install the app, why make it so hard? So either create an admin user/pass during setup or let the app create a default user and set it so they have to at minimum on first successful login set a new password before the login screen disappears and the full app is unlocked?