[Support]: Can't access WebUI, and can't figure out admin password #15721
Replies: 10 comments 8 replies
-
|
You can reset the admin password as shown here: https://docs.frigate.video/configuration/authentication#resetting-admin-password |
Beta Was this translation helpful? Give feedback.
-
|
Maybe it's me but the frigate documentation doesn't contain enough detail. After adding those lines, then what? |
Beta Was this translation helpful? Give feedback.
-
|
100% with you on this |
Beta Was this translation helpful? Give feedback.
-
|
"in the logs on next startup" |
Beta Was this translation helpful? Give feedback.
-
|
Just in case someone in the future runs into the same stupid issue as me: I wasn't seeing the password in the logs bc I forgot that at some point due to too much verbosity in the logs I turned down the logging level, setting it back to |
Beta Was this translation helpful? Give feedback.
-
|
Adding to @Licanueto my logging level in my config was set to warning, and so even though I had reset_admin_password: true, I wasn't able to see the new admin password print in the logs, so had to go using the :5000 trick to set up the admin password instead. It might be a good idea to log the admin password at an error level? |
Beta Was this translation helpful? Give feedback.
-
|
If someone can't figure out, what to look at in the logs, there is the example: |
Beta Was this translation helpful? Give feedback.
-
|
Thanks for the info here. It would be so much simpler if they updated frigate to, say, log the password to a temporary file in the config folder (ie: "DELETE_ME_TMP_PASSWORD" - and optionally prevent startup next time unless the file is deleted to enforce security) or let you specify it via ENV variable on first-time setup (a lot of docker-compose based services take this approach, with passwords often placed in the .env file). |
Beta Was this translation helpful? Give feedback.
-
|
The approach Frigate takes is used in other software like VSCode and Jupyter. Putting the password in a file is not secure, as other software may have access to the file system, but no other software should have access to the logs. In any case, it will likely stay the same until we implement a startup wizard in which case you would just define your password in the beginning. |
Beta Was this translation helpful? Give feedback.
-
|
Adding another item to the list of stupid mistakes one can make when using the
The correct username is |
Beta Was this translation helpful? Give feedback.
-
|
We've made changes for the next version of Frigate (0.17) to show a card on the login page with help text after resetting the password and when onboarding for the first time. The text also includes a link to the auth section of the official documentation. This should make it much less confusing for users. |
Beta Was this translation helpful? Give feedback.
-
|
Just wanted to quickly drop a line here: the software you are building here is incredibly polished and stable! And "tiny" improvements like this go a long way ("tiny" in the sense that it's a usability/workflow improvement in an edge-case, not saying that stuff like that is easy to implement or only a tiny bit of work or anything). Keep up the incredible work!! |
Beta Was this translation helpful? Give feedback.
-
|
I've just been through the same problem. Set the system up reasonably easily on OpenSuse but could not find the password anywhere. Tried the password reset and still nothing. All I did was use the setup instructions and then tried to find the password. Eventually resorted to using the 5000 method to get in. One thing that surprised me is that the setup creates a default camera and that results in the log having lots of failed messages. |
Beta Was this translation helpful? Give feedback.
-
|
a default camera is only added if you haven't created your own config file |
Beta Was this translation helpful? Give feedback.
-
|
Point noted but the installation intructions tell you how to install Frigate, including the yml file and that the best way to set thiings up is using docker compose, which is exactly what I did. |
Beta Was this translation helpful? Give feedback.
-
|
If you had been following the getting started guide you wouldn't have had that happen, as it instructs users to create the config file before starting, which is what I was alluding to https://docs.frigate.video/guides/getting_started |
Beta Was this translation helpful? Give feedback.
-
|
I can see that now but I started at the Installation section which refers to using Docker Compose as the recomended install method. I probably jumped the gun by doing the install at that point. Bottom line is that I did manage to get it up and running and amended the default camera settings to work with my Riello camera, at least to the point where I can see it on a browser. |
Beta Was this translation helpful? Give feedback.
-
|
I've just been through the same problem. Set the system up reasonably easily on OpenSuse but could not find the password anywhere. Tried the password reset and still nothing. All I did was use the setup instructions and then tried to find the password. Eventually resorted to using the 5000 method to get in. One thing that surprised me is that the setup creates a default camera and that results in the log having lots of failed messages. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Describe the problem you are having
Hey team. I am brand new to this and have been really struggling getting this set up. I've been following this guide: https://www.homeautomationguy.io/blog/running-frigate-on-proxmox
I got the container running and Frigate started up according to the logs. But I have 2 problems:
I am supposed to be able to access the WebUI at the URL of the proxmox container. For me, this is 192.168.50.83. The frigate port says to go to :8971, so for me, https://192.168.50.83:8971. But my browser finds nothing when I type that in. I tried going to port 5000, which is what the guide I'm following recommends, but my browser doesn't find that either. Help??
I am supposed to look at the logs to find the default password for the admin account to log into the WebUI. I can't find anything in the logs related to a password. What does this look like? My logs are attached.
Possibly relevant info: I don't have any real info for my cameras in the config file yet. I just copied the default config file with the dummy camera from the documentation. I figured I would add that later once I understood how. But I'm not sure if an actual camera config is needed to get this part working?
Would appreciate any help!!
Version
Can't access Web UI!
What browser(s) are you using?
No response
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
No response
Install method
Proxmox via Docker
docker-compose file or Docker CLI command
Object Detector
Coral
Network connection
Wired
Camera make and model
None set up yet
Screenshots of the Frigate UI's System metrics pages
No response
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions