[Support]: Take lot of time to start the Addon Frigate on the HA more then 2 or 3 hours , and some time does'nt start... #22045
Replies: 2 comments 5 replies
-
|
Based on the logs showing The logs indicate nginx is trying to reach the auth service at Since you mentioned this setup worked for over a year and you're running Proxmox with a Coral TPU passed through, there are a few things to check: For Coral TPU detection issues in Home Assistant OS: When running Frigate through the Home Assistant OS, you may need to run the Full Access variant of the Frigate Add-on with the Protection mode switch disabled so that the coral can be accessed.(2) For Proxmox passthrough: When running Frigate in a VM, you must ensure both device IDs are mapped for the USB coral. The USB coral has different IDs when it is uninitialized ( Recommended troubleshooting steps:
Without seeing your full configuration file and complete Frigate startup logs, it's difficult to pinpoint the exact cause, but the authentication service failures suggest the main Frigate process is crashing or failing to start completely, which could be related to the Coral TPU initialization. 📚 Sources: Have another question? Just tag @inkeep. |
Beta Was this translation helpful? Give feedback.
-
|
I'd suggest looking at the HAOS supervisor logs. How much RAM does your system have? HAOS is very aggressive about memory pressure. |
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
I have the frigate addon instaled on the HA Home Assistant
Installation method
Home Assistant OS
Core
2026.2.2
Supervisor
2026.02.2
Operating System
17.1
Frontend
20260128.6
Frigate Beta
Current version: 0.17.0-rc2
Installed on the proxmox with a coral TPU
Hello to all
I'm facing a very stranger issue with the frigate addon installed on the HA, is taking several time to start and some times doesn't start, the same configuration always work without any issue during more then a year... And now I'm facing this issue
On the logs still apears the following:
HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2026-02-19 11:50:56.986021531 2026/02/19 11:50:56 [error] 212#212: *72 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
2026-02-19 11:51:02.021374278 2026/02/19 11:51:02 [error] 212#212: *74 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2026-02-19 11:51:02.021378935 2026/02/19 11:51:02 [error] 212#212: *74 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", host: "127.0.0.1:5000"
Can some one please help me in order try solve this issue?
Thank you in advance for your support and best regards
Version
Current version: 0.17.0-rc2
What browser(s) are you using?
Versão 144.0.7559.133
Frigate config file
Relevant Frigate log output
Relevant go2rtc log output
FFprobe output from your camera
Frigate stats
No response
Install method
Home Assistant Add-on
docker-compose file or Docker CLI command
N/AObject Detector
Coral
Network connection
Wired
Camera make and model
several models
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