Installation de frigate

[doublemetre]

Bonjour à tous,

je commence avec home assistant que j’ai installé sur mon serveur qnap en machine virtuel.

j’adore home assistant et maintenant j’aimerai installer mes caméras dahua.

j’ai donc installer Frigate full (car j’ai une google coral usb) et là je rencontre pleins d’erreur au lancement et après il plante et redémarre.

j’ai plusieurs question, si j’ai bien compris je n’ai pas besoin d’installer go2rtc, il est déjà dans frigate?

quand je branche le coral il n’y a rien besoin de faire saut le déclarer dans frigate.yml?

autre question le frigate.yml que je modifie avec file éditor quand je le modifie il n’est pas repris dans l’appiquation frigate / éditeur y en a t-il 2 ?

Merci d’avance pour vos réponses et votre aide.

frigate.yml

mqtt:
enabled: true
host: http://192.168.1.137
user: mqtt_frigate
password: \*\*\*\*\*

go2rtc:
streams:
camera-1:
rtsp://xxx:xxx@192.168.14.55:554/cam/realmonitor?channel=1&subtype=0

ffmpeg:
hwaccel_args: preset-rpi-64-h264

detectors:
coral:
type: edgetpu
device: usb

cameras:
Camera-1: # <------ Name the camera
enabled: true
ffmpeg:
inputs:

* path: rtsp://127.0.0.1:8554/camera-1
  roles:
* detect
  detect:
  enabled: false # <---- disable detection until you have a working camera feed
  width: 1260
  height: 720

et mon log:

s6-rc: info: service nginx-log successfully stopped
2025-09-03 23:33:35.501533902  [2025-09-04 01:33:35] frigate.app                    INFO    : Stopping...
2025-09-03 23:33:35.540583522  [2025-09-04 01:33:35] frigate.ptz.autotrack          INFO    : Exiting autotracker...
2025-09-03 23:33:35.554318549  [2025-09-04 01:33:35] frigate.watchdog               INFO    : Exiting watchdog...
2025-09-03 23:33:35.570525864  [2025-09-04 01:33:35] frigate.stats.emitter          INFO    : Exiting stats emitter...
2025-09-03 23:33:35.609546359  [2025-09-04 01:33:35] frigate.storage                INFO    : Exiting storage maintainer...
2025-09-03 23:33:35.623762247  [2025-09-04 01:33:35] frigate.events.cleanup         INFO    : Exiting event cleanup...
2025-09-03 23:33:35.630317925  [2025-09-04 01:33:35] frigate.record.cleanup         INFO    : Exiting recording cleanup...
2025-09-03 23:33:35.635081325  [2025-09-04 01:33:35] frigate.ptz.onvif              INFO    : Exiting ONVIF controller...
2025-09-03 23:33:35.649141601  [2025-09-04 01:33:35] frigate.app                    INFO    : Waiting for capture process for Camera-1 to stop
2025-09-03 23:33:35.665526965  [2025-09-04 01:33:35] frigate.track.object_processing INFO    : Exiting object processor...
2025-09-03 23:33:35.803824151  [2025-09-04 01:33:35] watchdog.Camera-1              INFO    : Terminating the existing ffmpeg process...
2025-09-03 23:33:35.822765864  [2025-09-04 01:33:35] watchdog.Camera-1              INFO    : Waiting for ffmpeg to exit gracefully...
2025-09-03 23:33:35.872163042  [2025-09-04 01:33:35] frigate.events.maintainer      INFO    : Exiting event processor...
2025-09-03 23:33:36.312981361  [2025-09-04 01:33:36] frigate.app                    INFO    : Waiting for process for Camera-1 to stop
2025-09-03 23:33:36.824441346  [2025-09-04 01:33:36] frigate.video                  INFO    : Camera-1: emptying frame queue
2025-09-03 23:33:36.824455584  [2025-09-04 01:33:36] frigate.video                  INFO    : Camera-1: exiting subprocess
2025-09-03 23:33:36.871219900  [2025-09-04 01:33:36] frigate.app                    INFO    : Closing frame queue for Camera-1
2025-09-03 23:33:37.874398720  [2025-09-04 01:33:37] frigate.app                    INFO    : Detection queue closed
2025-09-03 23:33:38.376825548  [2025-09-04 01:33:38] frigate.app                    INFO    : Detected frames queue closed
2025-09-03 23:33:38.881106566  [2025-09-04 01:33:38] frigate.app                    INFO    : Timeline queue closed
2025-09-03 23:33:40.800176758  [2025-09-04 01:33:40] frigate.output.output          INFO    : exiting output process...
2025-09-03 23:33:43.134224462  [2025-09-04 01:33:43] frigate.record.maintainer      INFO    : Exiting recording maintenance...
2025-09-03 23:33:43.668465649  [2025-09-04 01:33:43] frigate.review.maintainer      INFO    : Exiting review maintainer...
2025-09-03 23:33:43.698990738  [2025-09-04 01:33:43] frigate.comms.webpush          INFO    : Closing notification queue
2025-09-03 23:33:44.163583741  [2025-09-04 01:33:44] frigate.comms.ws               INFO    : Exiting websocket client...
2025-09-03 23:33:45.163812945  [2025-09-04 01:33:45] peewee.sqliteq                 INFO    : writer received shutdown request, exiting.
2025-09-03 23:33:45.413837019  [INFO] Service Frigate exited with code 0 (by signal 0)
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
s6-rc: info: service frigate-log successfully stopped
2025-09-03 23:33:45.459397178  exit with signal: terminated
2025-09-03 23:33:45.532173892  [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service prepare: stopping
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service prepare successfully stopped
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 prepare: starting
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 frigate-log successfully started
s6-rc: info: service go2rtc-log successfully started
s6-rc: info: service certsync-log successfully started
s6-rc: info: service prepare successfully started
s6-rc: info: service go2rtc: starting
s6-rc: info: service go2rtc successfully started
s6-rc: info: service go2rtc-healthcheck: starting
s6-rc: info: service frigate: starting
s6-rc: info: service go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2025-09-03 23:33:56.997942642  [INFO] Starting NGINX...
2025-09-03 23:33:57.601899211  [INFO] No TLS certificate found. Generating a self signed certificate...
2025-09-03 23:33:58.357995289  [INFO] Preparing Frigate...
2025-09-03 23:34:01.625105487  [INFO] Preparing new go2rtc config...
2025-09-03 23:34:01.960786286  [INFO] Got IP address from supervisor: 192.168.14.137
2025-09-03 23:34:02.272897334  [INFO] Got WebRTC port from supervisor: 8555
2025-09-03 23:34:03.329859644  [INFO] Starting Frigate...
2025-09-03 23:34:06.875922008  [INFO] Starting go2rtc healthcheck service...
2025-09-03 23:34:08.116771405  [INFO] Starting go2rtc...
2025-09-03 23:34:08.365494701  01:34:08.364 INF go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
2025-09-03 23:34:08.367056892  01:34:08.366 INF config path=/dev/shm/go2rtc.yaml
2025-09-03 23:34:08.378824266  01:34:08.378 INF [api] listen addr=:1984
2025-09-03 23:34:08.380591056  01:34:08.379 INF [rtsp] listen addr=:8554
2025-09-03 23:34:08.385506568  01:34:08.385 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-09-03 23:34:31.080874252  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2025-09-03 23:34:32.931888013  2025/09/04 01:34:32 [error] 262#262: *1 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-09-03 23:34:32.931905125  2025/09/04 01:34:32 [error] 262#262: *1 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-09-03 23:34:35.382838108  127.0.0.1 - - [04/Sep/2025:01:34:35 +0200] "" 400 0 "-" "-" "-"
2025-09-03 23:34:35.822354813  [2025-09-04 01:34:35] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-09-03 23:34:35.928337405  [2025-09-04 01:34:35] frigate.util.config            INFO    : frigate config does not need migration...
2025-09-03 23:34:36.297819945  [2025-09-04 01:34:36] frigate.util.services          WARNING : Did not detect hwaccel, using a GPU for accelerated video decoding is highly recommended
2025-09-03 23:34:36.396480826  [2025-09-04 01:34:36] frigate.app                    INFO    : Starting Frigate (0.16.0-c2f8de9)
2025-09-03 23:34:36.401883509  [2025-09-04 01:34:36] frigate.app                    INFO    : Creating directory: /tmp/cache
2025-09-03 23:34:36.527699103  [2025-09-04 01:34:36] peewee_migrate.logs            INFO    : Starting migrations
2025-09-03 23:34:36.592683308  [2025-09-04 01:34:36] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-09-03 23:34:36.831809741  [2025-09-04 01:34:36] frigate.app                    INFO    : Recording process started: 449
2025-09-03 23:34:36.852881037  [2025-09-04 01:34:36] frigate.app                    INFO    : Review process started: 461
2025-09-03 23:34:36.901319033  [2025-09-04 01:34:36] frigate.app                    INFO    : go2rtc process pid: 130
2025-09-03 23:34:37.041802833  [2025-09-04 01:34:37] detector.coral                 INFO    : Starting detection process: 476
2025-09-03 23:34:37.054571088  [2025-09-04 01:34:37] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2025-09-03 23:34:37.065819476  [2025-09-04 01:34:37] frigate.detectors.plugins.edgetpu_tfl ERROR   : No EdgeTPU was detected. If you do not have a Coral device yet, you must configure CPU detectors.
2025-09-03 23:34:37.099831551  Process detector:coral:
2025-09-03 23:34:37.099843826  Traceback (most recent call last):
2025-09-03 23:34:37.099849239    File "/usr/local/lib/python3.11/dist-packages/tflite_runtime/interpreter.py", line 166, in load_delegate
2025-09-03 23:34:37.099861814      delegate = Delegate(library, options)
2025-09-03 23:34:37.099867539                 ^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-09-03 23:34:37.099872914    File "/usr/local/lib/python3.11/dist-packages/tflite_runtime/interpreter.py", line 104, in __init__
2025-09-03 23:34:37.099946488      raise ValueError(capture.message)
2025-09-03 23:34:37.099950388  ValueError
2025-09-03 23:34:37.099954188  
2025-09-03 23:34:37.099958300  During handling of the above exception, another exception occurred:
2025-09-03 23:34:37.099960988  
2025-09-03 23:34:37.099964200  Traceback (most recent call last):
2025-09-03 23:34:37.099968550    File "/usr/lib/python3.11/multiprocessing/process.py", line 314, in _bootstrap
2025-09-03 23:34:37.100048425      self.run()
2025-09-03 23:34:37.100053963    File "/opt/frigate/frigate/util/process.py", line 41, in run_wrapper
2025-09-03 23:34:37.100058013      return run(*args, **kwargs)
2025-09-03 23:34:37.100061325             ^^^^^^^^^^^^^^^^^^^^
2025-09-03 23:34:37.100065575    File "/usr/lib/python3.11/multiprocessing/process.py", line 108, in run
2025-09-03 23:34:37.100132174      self._target(*self._args, **self._kwargs)
2025-09-03 23:34:37.100137862    File "/opt/frigate/frigate/object_detection/base.py", line 112, in run_detector
2025-09-03 23:34:37.100142787      object_detector = LocalObjectDetector(detector_config=detector_config)
2025-09-03 23:34:37.100146974                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-09-03 23:34:37.100152474    File "/opt/frigate/frigate/object_detection/base.py", line 57, in __init__
2025-09-03 23:34:37.100156387      self.detect_api = create_detector(detector_config)
2025-09-03 23:34:37.100160212                        ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-09-03 23:34:37.100222212    File "/opt/frigate/frigate/detectors/__init__.py", line 18, in create_detector
2025-09-03 23:34:37.100226737      return api(detector_config)
2025-09-03 23:34:37.100229962             ^^^^^^^^^^^^^^^^^^^^
2025-09-03 23:34:37.100234412    File "/opt/frigate/frigate/detectors/plugins/edgetpu_tfl.py", line 42, in __init__
2025-09-03 23:34:37.100240574      edge_tpu_delegate = load_delegate("libedgetpu.so.1.0", device_config)
2025-09-03 23:34:37.100244874                          ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
2025-09-03 23:34:37.100250074    File "/usr/local/lib/python3.11/dist-packages/tflite_runtime/interpreter.py", line 168, in load_delegate
2025-09-03 23:34:37.100338061      raise ValueError('Failed to load delegate from {}\n{}'.format(
2025-09-03 23:34:37.100343248  ValueError: Failed to load delegate from libedgetpu.so.1.0
2025-09-03 23:34:37.100345761  
2025-09-03 23:34:37.322810710  [2025-09-04 01:34:37] frigate.app                    INFO    : Output process started: 499
2025-09-03 23:34:37.477457132  [2025-09-04 01:34:37] frigate.app                    INFO    : Camera processor started for Camera-1: 522
2025-09-03 23:34:38.227302160  2025/09/04 01:34:38 [error] 263#263: *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-09-03 23:34:38.228875439  2025/09/04 01:34:38 [error] 263#263: *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-09-03 23:34:38.421824286  [2025-09-04 01:34:38] frigate.app                    INFO    : Capture process started for Camera-1: 545
2025-09-03 23:34:38.610522471  [2025-09-04 01:34:38] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-09-03 23:34:39.625044871  [2025-09-04 01:34:39] frigate.api.fastapi_app        INFO    : FastAPI started
2025-09-03 23:34:58.644608501  [2025-09-04 01:34:58] frigate.watchdog               INFO    : Detection appears to have stopped. Exiting Frigate...
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-09-03 23:34:58.896801453  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
s6-rc: info: service certsync successfully stopped
s6-rc: info: service nginx: stopping
2025-09-03 23:34:58.995752037  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service certsync-log: stopping
s6-rc: info: service go2rtc-healthcheck successfully stopped
s6-rc: info: service certsync-log successfully stopped
2025-09-03 23:34:59.289287182  [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 nginx-log successfully stopped
2025-09-03 23:34:59.574788335  [2025-09-04 01:34:59] frigate.app                    INFO    : Stopping...
2025-09-03 23:34:59.621104237  [2025-09-04 01:34:59] frigate.stats.emitter          INFO    : Exiting stats emitter...
2025-09-03 23:34:59.649794040  [2025-09-04 01:34:59] frigate.events.cleanup         INFO    : Exiting event cleanup...
2025-09-03 23:34:59.660563192  [2025-09-04 01:34:59] frigate.watchdog               INFO    : Exiting watchdog...
2025-09-03 23:34:59.695278760  [2025-09-04 01:34:59] frigate.ptz.autotrack          INFO    : Exiting autotracker...
2025-09-03 23:34:59.714073155  [2025-09-04 01:34:59] frigate.storage                INFO    : Exiting storage maintainer...
2025-09-03 23:34:59.794344419  [2025-09-04 01:34:59] frigate.record.cleanup         INFO    : Exiting recording cleanup...
2025-09-03 23:34:59.875755663  [2025-09-04 01:34:59] frigate.ptz.onvif              INFO    : Exiting ONVIF controller...
2025-09-03 23:35:00.029149618  [2025-09-04 01:34:59] frigate.events.maintainer      INFO    : Exiting event processor...
2025-09-03 23:35:00.127882701  [2025-09-04 01:34:59] frigate.app                    INFO    : Waiting for capture process for Camera-1 to stop
2025-09-03 23:35:00.255157863  [2025-09-04 01:35:00] watchdog.Camera-1              INFO    : Terminating the existing ffmpeg process...
2025-09-03 23:35:00.271576396  [2025-09-04 01:35:00] watchdog.Camera-1              INFO    : Waiting for ffmpeg to exit gracefully...
2025-09-03 23:35:00.375251678  [2025-09-04 01:35:00] frigate.track.object_processing INFO    : Exiting object processor...
2025-09-03 23:35:01.091215493  [2025-09-04 01:35:01] frigate.app                    INFO    : Waiting for process for Camera-1 to stop
2025-09-03 23:35:01.266891470  [2025-09-04 01:35:01] frigate.video                  INFO    : Camera-1: emptying frame queue
2025-09-03 23:35:01.298829154  [2025-09-04 01:35:01] frigate.video                  INFO    : Camera-1: exiting subprocess
2025-09-03 23:35:01.432236707  [2025-09-04 01:35:01] frigate.app                    INFO    : Closing frame queue for Camera-1
2025-09-03 23:35:02.440869540  [2025-09-04 01:35:02] frigate.app                    INFO    : Detection queue closed
2025-09-03 23:35:02.946151530  [2025-09-04 01:35:02] frigate.app                    INFO    : Detected frames queue closed
2025-09-03 23:35:03.468132928  [2025-09-04 01:35:03] frigate.app                    INFO    : Timeline queue closed
2025-09-03 23:35:05.604189746  [2025-09-04 01:35:05] frigate.output.output          INFO    : exiting output process...
2025-09-03 23:35:06.826923397  [2025-09-04 01:35:06] frigate.record.maintainer      INFO    : Exiting recording maintenance...
2025-09-03 23:35:06.961012230  [2025-09-04 01:35:06] frigate.review.maintainer      INFO    : Exiting review maintainer...
2025-09-03 23:35:07.042339398  [2025-09-04 01:35:07] frigate.comms.webpush          INFO    : Closing notification queue
2025-09-03 23:35:07.131284710  [2025-09-04 01:35:07] frigate.comms.ws               INFO    : Exiting websocket client...
2025-09-03 23:35:07.941301453  [2025-09-04 01:35:07] peewee.sqliteq                 INFO    : writer received shutdown request, exiting.
2025-09-03 23:35:08.148260700  [INFO] Service Frigate exited with code 0 (by signal 0)
s6-rc: info: service frigate successfully stopped
s6-rc: info: service go2rtc: stopping
s6-rc: info: service frigate-log: stopping
2025-09-03 23:35:08.177820208  exit with signal: terminated
s6-rc: info: service frigate-log successfully stopped
2025-09-03 23:35:08.337507559  [INFO] The go2rtc service exited with code 0 (by signal 0)
s6-rc: info: service go2rtc successfully stopped
s6-rc: info: service prepare: stopping
s6-rc: info: service go2rtc-log: stopping
s6-rc: info: service prepare successfully stopped
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

[Forhorse]

@doublemetre

j’ai plusieurs question, si j’ai bien compris je n’ai pas besoin d’installer go2rtc, il est déjà dans frigate?

quand je branche le coral il n’y a rien besoin de faire saut le déclarer dans frigate.yml?

go2rtc est déjà inclu avec Frigate… mais tu n’as normalement pas besoin de l’utiliser. En tout cas de base il n’est pas utile pour que Frigate fonctionne donc commence par une configuration simple sans lui. Voir la doc Frigate qui indique les cas où il est nécessaire.

Pour que le TPU Coral fonctionne le système hôte (HOAS si tu as installé Frigate en tant que module complementaire à HA, ou l’OS de ton serveur Qnap si tu as installé Frigate en Docker à part) a généralement besoin d’un driver. En tout cas chez moi c’était le cas pour un Coral en PCI-E, aussi bien avec un système de base sous Debian qu’avec mon serveur sous Unraid. ça serait étonnant que ça ne soit pas le cas pour les autres système.
Avec un Coral en USB je ne sais pas, j’ai pas d’expérience.

Mais pareil que pour go2rtc, avant de vouloir déclarer un détecteur hardware, commence par une configuration extrêmement basique. Une fois que tu as un Frigate qui démarre et qui tu affiches ta/tes caméra il sera temps d’étoffer la configuration.

EDIT : Et puis attention, le fichier de configuration c’est du YAML, l’indentation du texte est très importante. Tel que tu le présente là, ton fichier de configuration ne peut pas fonctionner.

[doublemetre]

Merci pour tes conseil.

alors j’ai refait mon frigate.yaml comme ceci

mqtt:
  enabled: False

cameras:
  dummy_camera: # <--- this will be changed to your actual camera later
    enabled: False
    ffmpeg:
      inputs:
        - path: xxx:xxx@192.168.14.54:1034/cam/realmonitor?channel=1&subtype=0
          roles:
            - detect

il démare mais j’ai cette erreur:

2025-09-04 08:56:53.357488275  2025/09/04 10:56:53 [error] 227#227: *1 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-09-04 08:56:53.357506000  2025/09/04 10:56:53 [error] 227#227: *1 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-09-04 08:56:54.584153606  2025/09/04 10:56:54 [error] 226#226: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "homeassistant.local:8123"
2025-09-04 08:56:54.586457895  2025/09/04 10:56:54 [error] 226#226: *3 auth request unexpected status: 502 while sending to client, client: 172.30.32.2, server: , request: "GET /ws HTTP/1.1", host: "homeassistant.local:8123"
2025-09-04 08:56:54.586473945  172.30.32.2 - - [04/Sep/2025:10:56:54 +0200] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36" "192.168.14.149, 172.30.32.1"
2025-09-04 08:56:58.928269340  127.0.0.1 - - [04/Sep/2025:10:56:58 +0200] "" 400 0 "-" "-" "-"
2025-09-04 08:56:58.996891659  2025/09/04 10:56:58 [error] 229#229: *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-09-04 08:56:58.998086897  2025/09/04 10:56:58 [error] 229#229: *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-09-04 08:57:00.674878263  2025/09/04 10:57:00 [error] 228#228: *8 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "homeassistant.local:8123"
2025-09-04 08:57:00.674893438  2025/09/04 10:57:00 [error] 228#228: *8 auth request unexpected status: 502 while sending to client, client: 172.30.32.2, server: , request: "GET /ws HTTP/1.1", host: "homeassistant.local:8123"
2025-09-04 08:57:00.674901488  172.30.32.2 - - [04/Sep/2025:10:57:00 +0200] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36" "192.168.14.149, 172.30.32.1"
2025-09-04 08:57:04.388354161  2025/09/04 10:57:04 [error] 227#227: *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-09-04 08:57:04.388370549  2025/09/04 10:57:04 [error] 227#227: *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-09-04 08:57:06.533791287  2025/09/04 10:57:06 [error] 227#227: *12 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "homeassistant.local:8123"
2025-09-04 08:57:06.533808361  2025/09/04 10:57:06 [error] 227#227: *12 auth request unexpected status: 502 while sending to client, client: 172.30.32.2, server: , request: "GET /ws HTTP/1.1", host: "homeassistant.local:8123"
2025-09-04 08:57:06.533816536  172.30.32.2 - - [04/Sep/2025:10:57:06 +0200] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36" "192.168.14.149, 172.30.32.1"
2025-09-04 08:57:09.627819845  2025/09/04 10:57:09 [error] 227#227: *14 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-09-04 08:57:09.627836458  2025/09/04 10:57:09 [error] 227#227: *14 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-09-04 08:57:12.522290776  2025/09/04 10:57:12 [error] 227#227: *16 connect() failed (111: Connection refused) while connecting to upstream, client: 172.30.32.2, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "homeassistant.local:8123"
2025-09-04 08:57:12.522535099  2025/09/04 10:57:12 [error] 227#227: *16 auth request unexpected status: 502 while sending to client, client: 172.30.32.2, server: , request: "GET /ws HTTP/1.1", host: "homeassistant.local:8123"
2025-09-04 08:57:12.522982482  172.30.32.2 - - [04/Sep/2025:10:57:12 +0200] "GET /ws HTTP/1.1" 500 579 "-" "Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/139.0.0.0 Safari/537.36" "192.168.14.149, 172.30.32.1"
2025-09-04 08:57:14.807526341  2025/09/04 10:57:14 [error] 227#227: *18 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: 

[doublemetre]

bonjour, j’ai un peu avancer j’ai bien mon flux vidéo qui s’affiche mais mon proccesseur tourne à fond, je verai ensuiste pour le google coral.

j’aimerais déjà me débarasser de cette erreur dans le log nginx:

error   | 2025-09-04 23:02:27 | error   | [error] 272#272: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth"
error   | 2025-09-04 23:02:27 | error   | [error] 272#272: *1 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"
error   | 2025-09-04 23:02:33 | error   | [error] 273#273: *3 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth"
error   | 2025-09-04 23:02:33 | error   | [error] 273#273: *3 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"
unknown | 2025-09-04 23:02:33 | unknown | 127.0.0.1 - - [05/Sep/2025:01:02:33 +0200] "" 400 0 "-" "-" "-"
error   | 2025-09-04 23:02:39 | error   | [error] 274#274: *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"
error   | 2025-09-04 23:02:39 | error   | [error] 274#274: *6 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"
error   | 2025-09-04 23:02:45 | error   | [error] 275#275: *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"
error   | 2025-09-04 23:02:45 | error   | [error] 275#275: *8 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"
error   | 2025-09-04 23:02:50 | error   | [error] 272#272: *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"
error   | 2025-09-04 23:02:50 | error   | [error] 272#272: *10 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"
error   | 2025-09-04 23:02:56 | error   | [error] 272#272: *12 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth"
error   | 2025-09-04 23:02:56 | error   | [error] 272#272: *12 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"
error   | 2025-09-04 23:03:02 | error   | [error] 272#272: *14 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth"
error   | 2025-09-04 23:03:02 | error   | [error] 272#272: *14 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"
error   | 2025-09-04 23:03:07 | error   | [error] 272#272: *16 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth"
error   | 2025-09-04 23:03:07 | error   | [error] 272#272: *16 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"
error   | 2025-09-04 23:03:14 | error   | [error] 272#272: *18 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth"
error   | 2025-09-04 23:03:14 | error   | [error] 272#272: *18 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"
error   | 2025-09-04 23:03:20 | error   | [error] 272#272: *20 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1", subrequest: "/auth"
error   | 2025-09-04 23:03:20 | error   | [error] 272#272: *20 auth request unexpected status: 502 while sending to client, client: 127.0.0.1, server: , request: "GET /api/version HTTP/1.1"

avez-vous une idée de ce qui pose problème? merci d’avance pour votre aide je suis perdu.

[Lap]

L’erreur laisse penser qu’il essai d’ouvrir un flux interne (127.xxx.xxx.xxx), comme la conf pour ouvrir un flux go2rtc.
Si ma lecture des logs est la bonne, la conf que tu nous a mis ci-dessus ne semble pas être appliquée

Quand tu vas dans l’éditeur de configuration web intégré à frigate, tu retrouve bien ta nouvelle conf ou tu as la précédente ?

[doublemetre]

oui c’est bien la nouvelle configuration.
faut-il installer webrtc ou est-il dans frigate?

[Forhorse]

Si tu utilises l’image standard, elle contient déjà tout ce qu’il faut pour que Frigate tourne.

[doublemetre]

ok merci pour tes conseilles.
je continue à chercher.

j’envisage de changer mon vieux nas qnap 453A ou tourne Home assistant OS sur un WM.
appart frigate je suis très content.

Maintenant j’ai lu que google coral ne fonctionne pas sur wm qnap.
donc ma question que me conseillez-vous comme matos pour faire tourner frigate et home assitant, je ne connais pas trop les contenaire je suis pas trop à laise avec le code.

Merci d’avance pour vos réponses.

[Lap]

Pour ton problème, est-ce que tu n’aurais pas, sur le même hôte que Frigate, un service qui essaierait de se connecter à frigate (via api par exemple), genre une conf home assistant ou truc du genre ?

Pour ta clé Coral, il faudra que tu modifie ta conf docker compose pour exposer ta clé USB au container frigate. D’orgine un containeur est cloisonné avec le systeme hote, et ne peux pas acceder librement au ressources systeme. (Et il faut aussi que ta clé coral soit bien reconnue par le systeme hote avant toute chose - drivers et autre - )

[alex71]

Salut,

Cette erreur n’est à priori pas un problème, voir la FAQ de la version 15 (la version 16 pointe aussi sur cette FAQ) qui traite de ce point ( rubrique Usage, point 4) :

Frigate 0.15 FAQ · blakeblackshear frigate · Discussion #16391

J’ai aussi cette erreur lors du démarrage pour info et tout fonctionne parfaitement de mon côté.

Aussi je note que ton fichier de config est en .yml alors qu’il faut maintenant qu’il soit en .yaml depuis une certaine mise à jour . Penses à bien supprimer le fichier .yml du dossier pour éviter de te mélanger les pinceaux

Frigate Configuration | Frigate

[doublemetre]

Merci pour votre aide.
je vais déjà corrigé mes erreurs.