[Support]: Can't connect to web UI after upgrading from v0.16.1 to v0.16.2 #20590
Replies: 3 comments 7 replies
|
Based on your logs, the issue appears to be that the Frigate authentication service isn't starting properly after upgrading to v0.16.2. The error messages show "Connection refused" when trying to connect to the auth service at port 5001(1). To troubleshoot this startup issue:
The authentication service failure suggests there may be an issue with the v0.16.2 container startup sequence or a configuration incompatibility that's preventing the internal services from initializing properly. 📚 Sources: Have another question? Just tag @inkeep. |
|
looks like it is just running the database vacuum, I don't see any errors indicating it is failing |
|
I have had a fun day with HA - webgui not available. Restarting the mini PC brought it back for a while. Then gone offline again. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Describe the problem you are having
I can no longer connect to the web UI after upgrading from v0.16.1 to v0.16.2 with errors in the logs.
I am hosting a stand-alone version of Frigate using Docker Compose. I'm able to get back up and running by manually setting the version back
0.16.1and restarting the container.Version
0.16.2
What browser(s) are you using?
Chromium 141.0.7390.76 specifically, but doesn't work from any browser.
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
No response
Install method
Docker Compose
docker-compose file or Docker CLI command
Object Detector
Coral
Network connection
Wired
Camera make and model
Various Reolink's
Screenshots of the Frigate UI's System metrics pages
No response
Any other information that may be helpful
No response
All reactions