[Config Support]: auth connect filed #12915
Replies: 9 comments 8 replies
-
Seems like Frigate is slow to start for some reason and it has not started yet. How long have you tried letting it sit? |
Beta Was this translation helpful? Give feedback.
-
I have the exact same situation:
|
Beta Was this translation helpful? Give feedback.
-
The same thing is happening here. Problem appeared after updating to this new version |
Beta Was this translation helpful? Give feedback.
-
Is it the Home Assistant Integration?
So for me its only two Frigate related things running on my HA-VM: The Integration inside HA Core and the Proxy Addon inside Supervisor.
I dont have any longer boot time for my frigate docker container with the 0.14 though. Id say it stayed the same. Maybe something in the HA-Addons is a bit slower now? //Edit: For me its not an error, that an error message comes up during start up when HA already tries to connect, the longer boot times for the other users could however indicate an issue. |
Beta Was this translation helpful? Give feedback.
-
i've been running into this as well. |
Beta Was this translation helpful? Give feedback.
-
I solved it on my side from one of these actions:
my cameras were all set to IPs that got changed with a new router, and the auth seemed related to failure to connect to cameras. so it seems like the frigate instance is incredible sensitive right now, and bad camera configs (bad ip) causes the entire service to die at startup |
Beta Was this translation helpful? Give feedback.
-
I have the same problem, have you solved it? |
Beta Was this translation helpful? Give feedback.
-
I'm observing the same issue using v0.14.1. On a Raspberry Pi 5 with 8GiB of RAM this also takes 2-3 mins to resolve. As I'd like to go with Hailo 8L anyway I'd probably try another more bleeding edge version. |
Beta Was this translation helpful? Give feedback.
-
Same issue here on 0.15 beta 2, it was perfectly working and seems to have reboot randomly before not starting at all for 30 minutes now. No change in config, no update, but i connected a new client to the MQTT broker, could it be linked ? |
Beta Was this translation helpful? Give feedback.
-
Describe the problem you are having
Today I switched to the updated stable version.
When starting Frigate, these errors occur, and they continue for 2-3 minutes, after frigate starts.
I don't use any authorization, as Frigate works as an add-on in HAos.
Tell me what I'm doing wrong.
Version
0.14.0
Frigate config file
Relevant log output
Frigate stats
No response
Operating system
HassOS
Install method
HassOS Addon
Object Detector
CPU (no coral)
Any other information that may be helpful
No response
Beta Was this translation helpful? Give feedback.
All reactions