Frigate addon failing to start in home assistant

[robertboccia]

Checklist

• I have updated to the latest available Frigate version.
• I have cleared the cache of my browser.
• I have tried a different browser to see if it is related to my browser.
• I have tried reproducing the issue in incognito mode to rule out problems with any third party extensions or plugins I have installed.

Describe the problem you are having

Frigate addon failing to start in home assistant

Steps to reproduce

Not sure how you reproduce addon failing to start

Version

Latest version 15.1

In which browser(s) are you experiencing the issue with?

App and edge and chrome

Frigate config file

CNt open frigate

docker-compose file or Docker CLI command

Don't use docker

Relevant Frigate log output

Frigate
2025-07-10 03:40:47.905784996  Thread 0x00007fb6ed8486c0 (most recent call first):
2025-07-10 03:40:47.905806719    File "/opt/frigate/frigate/comms/zmq_proxy.py", line 29 in run
2025-07-10 03:40:47.905833080    File "/usr/lib/python3.9/threading.py", line 954 in _bootstrap_inner
2025-07-10 03:40:47.905853185    File "/usr/lib/python3.9/threading.py", line 912 in _bootstrap
2025-07-10 03:40:47.905857704  
2025-07-10 03:40:47.905859112  Thread 0x00007fb6d07fc6c0 (most recent call first):
2025-07-10 03:40:47.905876779    File "/usr/lib/python3.9/threading.py", line 312 in wait
2025-07-10 03:40:47.905895217    File "/usr/lib/python3.9/queue.py", line 171 in get
2025-07-10 03:40:47.905930186    File "/usr/local/lib/python3.9/dist-packages/playhouse/sqliteq.py", line 162 in loop
2025-07-10 03:40:47.905967056    File "/usr/local/lib/python3.9/dist-packages/playhouse/sqliteq.py", line 137 in run
2025-07-10 03:40:47.906000168    File "/usr/local/lib/python3.9/dist-packages/playhouse/sqliteq.py", line 272 in run
2025-07-10 03:40:47.906017789    File "/usr/lib/python3.9/threading.py", line 892 in run
2025-07-10 03:40:47.906041587    File "/usr/lib/python3.9/threading.py", line 954 in _bootstrap_inner
2025-07-10 03:40:47.906062316    File "/usr/lib/python3.9/threading.py", line 912 in _bootstrap
2025-07-10 03:40:47.906063410  
2025-07-10 03:40:47.906068194  Thread 0x00007fb6c66b26c0 (most recent call first):
2025-07-10 03:40:47.906082391    File "/usr/lib/python3.9/threading.py", line 312 in wait
2025-07-10 03:40:47.906107443    File "/usr/lib/python3.9/multiprocessing/queues.py", line 233 in _feed
2025-07-10 03:40:47.906125875    File "/usr/lib/python3.9/threading.py", line 892 in run
2025-07-10 03:40:47.906150317    File "/usr/lib/python3.9/threading.py", line 954 in _bootstrap_inner
2025-07-10 03:40:47.906171029    File "/usr/lib/python3.9/threading.py", line 912 in _bootstrap
2025-07-10 03:40:47.906172122  
2025-07-10 03:40:47.906176894  Thread 0x00007fb6c6eb36c0 (most recent call first):
2025-07-10 03:40:47.906201096    File "/usr/lib/python3.9/multiprocessing/connection.py", line 379 in _recv
2025-07-10 03:40:47.906230559    File "/usr/lib/python3.9/multiprocessing/connection.py", line 414 in _recv_bytes
2025-07-10 03:40:47.906260158    File "/usr/lib/python3.9/multiprocessing/connection.py", line 216 in recv_bytes
2025-07-10 03:40:47.906283240    File "/usr/lib/python3.9/multiprocessing/queues.py", line 103 in get
2025-07-10 03:40:47.906307332    File "/usr/lib/python3.9/logging/handlers.py", line 1461 in dequeue
2025-07-10 03:40:47.906337717    File "/usr/lib/python3.9/logging/handlers.py", line 1512 in _monitor
2025-07-10 03:40:47.906356733    File "/usr/lib/python3.9/threading.py", line 892 in run
2025-07-10 03:40:47.906383905    File "/usr/lib/python3.9/threading.py", line 954 in _bootstrap_inner
2025-07-10 03:40:47.906407487    File "/usr/lib/python3.9/threading.py", line 912 in _bootstrap
2025-07-10 03:40:47.906408592  
2025-07-10 03:40:47.906413375  Thread 0x00007fb71e6f7740 (most recent call first):
2025-07-10 03:40:47.906429164    File "/usr/lib/python3.9/threading.py", line 1428 in _shutdown
2025-07-10 03:40:48.088978193  [INFO] Service Frigate exited with code 256 (by signal 6)
s6-rc: info: service legacy-services: stopping
s6-rc: info: service legacy-services successfully stopped
s6-rc: info: service go2rtc-healthcheck: stopping
s6-rc: info: service certsync: stopping
2025-07-10 03:40:48.093342346  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2025-07-10 03:40:48.093935651  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
s6-rc: info: service certsync successfully stopped
s6-rc: info: service nginx: stopping
s6-rc: info: service certsync-log: stopping
s6-rc: info: service certsync-log successfully stopped
2025-07-10 03:40:48.123722140  [INFO] Service NGINX exited with code 0 (by signal 0)
s6-rc: info: service nginx successfully stopped
s6-rc: info: service nginx-log: stopping
s6-rc: info: service frigate: stopping
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
s6-rc: info: service nginx-log successfully stopped
2025-07-10 03:40:48.125110023  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2025-07-10 03:40:48.127421406  [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service go2rtc-log successfully stopped
s6-rc: info: service log-prepare: stopping
s6-rc: info: service s6rc-fdholder: stopping
s6-rc: info: service log-prepare successfully stopped
s6-rc: info: service legacy-cont-init: stopping
s6-rc: info: service s6rc-fdholder successfully stopped
s6-rc: info: service legacy-cont-init successfully stopped
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped
s6-rc: info: service s6rc-fdholder: starting
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service s6rc-fdholder successfully started
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service log-prepare: starting
s6-rc: info: service log-prepare successfully started
s6-rc: info: service nginx-log: starting
s6-rc: info: service go2rtc-log: starting
s6-rc: info: service frigate-log: starting
s6-rc: info: service certsync-log: starting
s6-rc: info: service nginx-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service frigate-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
s6-rc: info: service go2rtc-healthcheck successfully started
2025-07-10 04:06:41.141688258  [INFO] Preparing new go2rtc config...
2025-07-10 04:06:41.141945655  [INFO] Preparing Frigate...
2025-07-10 04:06:41.142450707  [INFO] Starting NGINX...
2025-07-10 04:06:41.149989106  [INFO] No TLS certificate found. Generating a self signed certificate...
2025-07-10 04:06:41.170538911  [INFO] Got IP address from supervisor: 10.0.0.80
2025-07-10 04:06:41.199811057  [INFO] Got WebRTC port from supervisor: 8558
2025-07-10 04:06:41.215051270  [INFO] Starting Frigate...
2025-07-10 04:06:41.569611785  [INFO] Not injecting WebRTC candidates into go2rtc config as it has been set manually
2025-07-10 04:06:41.660878934  [INFO] Starting go2rtc...
2025-07-10 04:06:41.753639076  06:06:41.753 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2025-07-10 04:06:41.753642489  06:06:41.753 INF config path=/dev/shm/go2rtc.yaml
2025-07-10 04:06:41.753958740  06:06:41.753 INF [rtsp] listen addr=:8554
2025-07-10 04:06:41.753983190  06:06:41.753 INF [api] listen addr=:1984
2025-07-10 04:06:41.754182426  06:06:41.754 INF [webrtc] listen addr=:8555
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
2025-07-10 04:06:42.241729863  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2025-07-10 04:06:42.309316180  127.0.0.1 - - [10/Jul/2025:06:06:42 +0200] "" 400 0 "-" "-" "-"
2025-07-10 04:06:43.509368489  [2025-07-10 06:06:43] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-07-10 04:06:43.542650302  [2025-07-10 06:06:43] frigate.util.config            INFO    : frigate config does not need migration...
2025-07-10 04:06:43.670594605  [2025-07-10 06:06:43] frigate.util.services          INFO    : Automatically detected vaapi hwaccel for video decoding
2025-07-10 04:06:46.131121236  2025/07/10 06:06:46 [error] 199#199: *2 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"
2025-07-10 04:06:46.131134945  2025/07/10 06:06:46 [error] 199#199: *2 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"
2025-07-10 04:06:51.142427361  [INFO] Starting go2rtc healthcheck service...
2025-07-10 04:06:51.162031183  2025/07/10 06:06:51 [error] 200#200: *4 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"
2025-07-10 04:06:51.162043386  2025/07/10 06:06:51 [error] 200#200: *4 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"
2025-07-10 04:06:56.195777779  2025/07/10 06:06:56 [error] 201#201: *6 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"
2025-07-10 04:06:56.195790977  2025/07/10 06:06:56 [error] 201#201: *6 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"
2025-07-10 04:07:01.230268465  2025/07/10 06:07:01 [error] 202#202: *8 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"
2025-07-10 04:07:01.230281373  2025/07/10 06:07:01 [error] 202#202: *8 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"
2025-07-10 04:07:06.263696371  2025/07/10 06:07:06 [error] 199#199: *10 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"
2025-07-10 04:07:06.263709068  2025/07/10 06:07:06 [error] 199#199: *10 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"
2025-07-10 04:07:09.329462221  [2025-07-10 06:07:09] frigate.app                    INFO    : Starting Frigate (0.15.0-6cb5cfb)
2025-07-10 04:07:09.330026565  [2025-07-10 06:07:09] frigate.app

Relevant go2rtc log output

06:15:54.125 INF go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
06:15:54.125 INF config path=/config/go2rtc.yaml
06:15:54.125 INF [rtsp] listen addr=:8554
06:15:54.125 INF [api] listen addr=:1984
06:15:54.127 INF [webrtc] listen addr=:8555

Operating system

Home Assistant OS

Install method

Home Assistant Add-on

Network connection

Wired

Camera make and model

Sonoff

Screenshots of the Frigate UI's System metrics pages

Can't get into it since addon isn't starting

Any other information that may be helpful

No response

[vanruix]

Ditto here

[yousaf465]

MaxWinterstein/homeassistant-addons#365

check this this might be same issue

[hawkeye217]

This is a duplicate of #19073 and is an issue with HAOS 16.

Follow home-assistant/operating-system#4110 for updates.