Frigate does not start

Hello,
i try to use frigate addon in my home assistant. HA is installed on a proxmox.
yml config:

mqtt:
  enabled: true
  host: ip homeassistant
  user: user
  password: pw
  topic_prefix: frigate
  # Optional: client id (default: shown below)
  # WARNING: must be unique if you are running multiple instances
  client_id: frigate
  # Optional: interval in seconds for publishing stats (default: shown below)
  stats_interval: 60

ffmpeg:
  hwaccel_args: preset-vaapi

# Optional: Detectors configuration. Defaults to a single CPU detector
detectors:
  # Required: name of the detector
  detector_name:
    # Required: type of the detector
    # Frigate provided types include 'cpu', 'edgetpu', and 'openvino' (default: shown below)
    # Additional detector types can also be plugged in.
    # Detectors may require additional configuration.
    # Refer to the Detectors configuration page for more information.
    type: cpu 
birdseye:
  enabled: True
  restream: True
  mode: objects
objects:
  track:
    - person
    - car
  filters:
    person:
      min_area: 5000
      max_area: 100000
  cameras:
  annkec800: # <------ Name the camera
    ffmpeg:
      output_args:
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps
          1 -strftime 1 -c:v copy -tag:v hvc1 -bsf:v hevc_mp4toannexb -c:a aac
      inputs:
        - path: rtsp://rtsp path
            <----- Update for your camera
          roles:
            - detect
            
    detect:
      width: # <- optional, by default Frigate tries to automatically detect resolution
      height: # <- optional, by default Frigate tries to automatically detect resolution

i got this error:

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 certsync-log successfully started
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 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
2024-09-13 12:20:35.697596800  [INFO] Preparing new go2rtc config...
2024-09-13 12:20:35.697748835  [INFO] Preparing Frigate...
2024-09-13 12:20:35.700046391  [INFO] Starting NGINX...
2024-09-13 12:20:35.714692513  [INFO] No TLS certificate found. Generating a self signed certificate...
2024-09-13 12:20:35.720844808  [INFO] Starting Frigate...
2024-09-13 12:20:35.744809946  [INFO] Got IP address from supervisor: 192.168.178.64
2024-09-13 12:20:35.789825497  [INFO] Got WebRTC port from supervisor: 8550
2024-09-13 12:20:36.252624819  [INFO] Starting go2rtc...
2024-09-13 12:20:36.467537490  14:20:36.467 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-09-13 12:20:36.469772380  14:20:36.469 INF config path=/dev/shm/go2rtc.yaml
2024-09-13 12:20:36.470328936  14:20:36.470 INF [api] listen addr=:1984
2024-09-13 12:20:36.470788206  14:20:36.470 INF [rtsp] listen addr=:8554
2024-09-13 12:20:36.471401776  14:20:36.471 INF [webrtc] listen addr=:8555/tcp
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
s6-rc: info: service certsync successfully started
2024-09-13 12:20:37.506216591  [INFO] Starting certsync...
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2024-09-13 12:20:37.590787883  127.0.0.1 - - [13/Sep/2024:14:20:37 +0200] "" 400 0 "-" "-" "-"
2024-09-13 12:20:37.639819901  [2024-09-13 14:20:37] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2024-09-13 12:20:37.640307850  [2024-09-13 14:20:37] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-09-13 12:20:37.645538529  [2024-09-13 14:20:37] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-09-13 12:20:37.648544816  [2024-09-13 14:20:37] frigate.util.config            INFO    : copying config as backup...
2024-09-13 12:20:37.649106355  [2024-09-13 14:20:37] frigate.util.config            INFO    : Migrating frigate config from 0.13 to 0.14...
2024-09-13 12:20:37.655077866  [2024-09-13 14:20:37] frigate.util.config            INFO    : Migrating export file names...
2024-09-13 12:20:37.660660227  [2024-09-13 14:20:37] frigate.util.config            INFO    : Finished frigate config migration...
2024-09-13 12:20:37.662745463  *************************************************************
2024-09-13 12:20:37.662808820  *************************************************************
2024-09-13 12:20:37.662849839  ***    Your config file is not valid!                     ***
2024-09-13 12:20:37.662887705  ***    Please check the docs at                           ***
2024-09-13 12:20:37.662925239  ***    https://docs.frigate.video/configuration/index     ***
2024-09-13 12:20:37.662962780  *************************************************************
2024-09-13 12:20:37.663013581  *************************************************************
2024-09-13 12:20:37.663052581  ***    Config Validation Errors                           ***
2024-09-13 12:20:37.663089804  *************************************************************
2024-09-13 12:20:37.663222041  objects.cameras: Extra inputs are not permitted
2024-09-13 12:20:37.663280224  objects.annkec800: Extra inputs are not permitted
2024-09-13 12:20:37.663323091  cameras: Field required
2024-09-13 12:20:37.663363228  *************************************************************
2024-09-13 12:20:37.663410565  ***    End Config Validation Errors                       ***
2024-09-13 12:20:37.663448776  *************************************************************
2024-09-13 12:20:38.870436033  [INFO] Service Frigate exited with code 1 (by signal 0)
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
2024-09-13 12:20:38.881354725  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-09-13 12:20:38.882794866  [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
2024-09-13 12:20:38.907393330  [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
2024-09-13 12:20:38.915369811  exit with signal: terminated
2024-09-13 12:20:38.920779535  [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 frigate-log 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

can anybody help me to repair my configure?

Hi there!

Try to check the following:

1- Identation is very important when editing YAML files. Take a look at Frigate Configuration | Frigate. You can just copy and paste that sample configuration and see if starts.

2- You have some values as “True” and it should be “true”, all lowercase

Yes the sample works.
True is written in lower case everywhere, was corrected to upper case here in the forum when it was inserted.

bad indentation

I changed to cameras:
annkec800: Eingang
no succes

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-fdholder successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
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 go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2024-09-13 16:18:42.473309839  [INFO] Preparing Frigate...
2024-09-13 16:18:42.481974076  [INFO] Starting NGINX...
2024-09-13 16:18:42.483519428  [INFO] Preparing new go2rtc config...
2024-09-13 16:18:42.488964523  [INFO] Starting Frigate...
2024-09-13 16:18:42.497512299  [INFO] No TLS certificate found. Generating a self signed certificate...
2024-09-13 16:18:42.530954196  [INFO] Got IP address from supervisor: 192.168.178.64
2024-09-13 16:18:42.576762145  [INFO] Got WebRTC port from supervisor: 8550
2024-09-13 16:18:42.967426612  [INFO] Starting go2rtc...
2024-09-13 16:18:43.245737853  18:18:43.245 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-09-13 16:18:43.245931026  18:18:43.245 INF config path=/dev/shm/go2rtc.yaml
2024-09-13 16:18:43.247469697  18:18:43.247 INF [api] listen addr=:1984
2024-09-13 16:18:43.247591286  18:18:43.247 INF [rtsp] listen addr=:8554
2024-09-13 16:18:43.249086142  18:18:43.249 INF [webrtc] listen addr=:8555/tcp
2024-09-13 16:18:44.450067493  [2024-09-13 18:18:44] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2024-09-13 16:18:44.450281074  [2024-09-13 18:18:44] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-09-13 16:18:44.451003014  [2024-09-13 18:18:44] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-09-13 16:18:44.465799402  [2024-09-13 18:18:44] frigate.util.config            INFO    : frigate config does not need migration...
2024-09-13 16:18:44.473338900  *************************************************************
2024-09-13 16:18:44.473484594  *************************************************************
2024-09-13 16:18:44.473486627  ***    Your config file is not valid!                     ***
2024-09-13 16:18:44.473490229  ***    Please check the docs at                           ***
2024-09-13 16:18:44.473492249  ***    https://docs.frigate.video/configuration/index     ***
2024-09-13 16:18:44.473493681  *************************************************************
2024-09-13 16:18:44.473512447  *************************************************************
2024-09-13 16:18:44.473513845  ***    Config Validation Errors                           ***
2024-09-13 16:18:44.473515447  *************************************************************
2024-09-13 16:18:44.473516692  objects.cameras: Extra inputs are not permitted
2024-09-13 16:18:44.473517828  objects.annkec800: Extra inputs are not permitted
2024-09-13 16:18:44.473555437  cameras: Field required
2024-09-13 16:18:44.473556892  *************************************************************
2024-09-13 16:18:44.473777893  ***    End Config Validation Errors                       ***
2024-09-13 16:18:44.473779693  *************************************************************
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
2024-09-13 16:18:44.885737126  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2024-09-13 16:18:44.951594896  127.0.0.1 - - [13/Sep/2024:18:18:44 +0200] "" 400 0 "-" "-" "-"
2024-09-13 16:18:45.661734269  [INFO] Service Frigate exited with code 1 (by signal 0)
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
2024-09-13 16:18:45.671673912  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
2024-09-13 16:18:45.673856255  [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
2024-09-13 16:18:45.695888377  [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
2024-09-13 16:18:45.700512969  exit with signal: terminated
s6-rc: info: service nginx-log successfully stopped
s6-rc: info: service frigate-log successfully stopped
2024-09-13 16:18:45.705630288  [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

No, the problem is indentation

cameras should not have any spaces before it

cameras: 
    annkec800:eingang
    ffmpeg:
      output_args:
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps
          1 -strftime 1 -c:v copy -tag:v hvc1 -bsf:v hevc_mp4toannexb -c:a aac

another error:

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-fdholder successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
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 certsync-log successfully started
s6-rc: info: service frigate-log successfully started
s6-rc: info: service go2rtc-log 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
2024-09-13 16:59:39.749524702  [INFO] Preparing Frigate...
s6-rc: info: service go2rtc-healthcheck successfully started
2024-09-13 16:59:39.750712483  [INFO] Preparing new go2rtc config...
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2024-09-13 16:59:39.765006525  [INFO] Starting NGINX...
2024-09-13 16:59:39.766251628  [INFO] Starting Frigate...
2024-09-13 16:59:39.781377226  [INFO] No TLS certificate found. Generating a self signed certificate...
2024-09-13 16:59:39.822953444  [INFO] Got IP address from supervisor: 192.168.178.64
2024-09-13 16:59:39.883960902  [INFO] Got WebRTC port from supervisor: 8550
2024-09-13 16:59:40.238637040  [INFO] Starting go2rtc...
2024-09-13 16:59:40.361655228  18:59:40.361 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-09-13 16:59:40.361966224  18:59:40.361 INF config path=/dev/shm/go2rtc.yaml
2024-09-13 16:59:40.363022089  18:59:40.362 INF [api] listen addr=:1984
2024-09-13 16:59:40.363590992  18:59:40.363 INF [rtsp] listen addr=:8554
2024-09-13 16:59:40.364061107  18:59:40.364 INF [webrtc] listen addr=:8555/tcp
s6-rc: info: service nginx successfully started
s6-rc: info: service certsync: starting
2024-09-13 16:59:41.235403984  [INFO] Starting certsync...
s6-rc: info: service certsync successfully started
s6-rc: info: service legacy-services: starting
s6-rc: info: service legacy-services successfully started
2024-09-13 16:59:41.319675738  127.0.0.1 - - [13/Sep/2024:18:59:41 +0200] "" 400 0 "-" "-" "-"
2024-09-13 16:59:42.095412609  [2024-09-13 18:59:42] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2024-09-13 16:59:42.096565456  [2024-09-13 18:59:42] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-09-13 16:59:42.096684337  [2024-09-13 18:59:42] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-09-13 16:59:42.110315007  [2024-09-13 18:59:42] frigate.util.config            INFO    : frigate config does not need migration...
2024-09-13 16:59:42.113196940  *************************************************************
2024-09-13 16:59:42.113199584  *************************************************************
2024-09-13 16:59:42.113202947  ***    Your config file is not valid!                     ***
2024-09-13 16:59:42.113204893  ***    Please check the docs at                           ***
2024-09-13 16:59:42.113206190  ***    https://docs.frigate.video/configuration/index     ***
2024-09-13 16:59:42.113226538  *************************************************************
2024-09-13 16:59:42.113227798  *************************************************************
2024-09-13 16:59:42.113229353  ***    Config Validation Errors                           ***
2024-09-13 16:59:42.113230608  *************************************************************
2024-09-13 16:59:42.113277975  'ffmpeg'
2024-09-13 16:59:42.120493903  Traceback (most recent call last):
2024-09-13 16:59:42.120496467    File "/opt/frigate/frigate/app.py", line 645, in start
2024-09-13 16:59:42.120497663      self.init_config()
2024-09-13 16:59:42.120498924    File "/opt/frigate/frigate/app.py", line 139, in init_config
2024-09-13 16:59:42.120500141      user_config = FrigateConfig.parse_file(config_file)
2024-09-13 16:59:42.120501323    File "/opt/frigate/frigate/config.py", line 1660, in parse_file
2024-09-13 16:59:42.120502415      return cls.model_validate(config)
2024-09-13 16:59:42.120503621    File "/usr/local/lib/python3.9/dist-packages/pydantic/main.py", line 551, in model_validate
2024-09-13 16:59:42.120504742      return cls.__pydantic_validator__.validate_python(
2024-09-13 16:59:42.120505846    File "/opt/frigate/frigate/config.py", line 1048, in __init__
2024-09-13 16:59:42.120508097      if len(config["ffmpeg"]["inputs"]) == 1:
2024-09-13 16:59:42.120509102  KeyError: 'ffmpeg'
2024-09-13 16:59:42.120536871  
2024-09-13 16:59:42.120538198  *************************************************************
2024-09-13 16:59:42.120539332  ***    End Config Validation Errors                       ***
2024-09-13 16:59:42.120553785  *************************************************************
2024-09-13 16:59:44.654885586  2024/09/13 18:59:44 [error] 175#175: *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"
2024-09-13 16:59:44.654904729  2024/09/13 18:59:44 [error] 175#175: *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"
2024-09-13 16:59:49.699555912  2024/09/13 18:59:49 [error] 176#176: *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"
2024-09-13 16:59:49.699559807  2024/09/13 18:59:49 [error] 176#176: *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"
2024-09-13 16:59:49.748054223  [INFO] Starting go2rtc healthcheck service...
2024-09-13 16:59:54.750180724  2024/09/13 18:59:54 [error] 175#175: *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"
2024-09-13 16:59:54.750184579  2024/09/13 18:59:54 [error] 175#175: *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"
2024-09-13 16:59:59.792690610  2024/09/13 18:59:59 [error] 175#175: *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"
2024-09-13 16:59:59.792700838  2024/09/13 18:59:59 [error] 175#175: *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"
2024-09-13 17:00:04.825332672  2024/09/13 19:00:04 [error] 175#175: *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"
2024-09-13 17:00:04.825336418  2024/09/13 19:00:04 [error] 175#175: *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"
2024-09-13 17:00:09.857011298  2024/09/13 19:00:09 [error] 175#175: *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", upstream: "http://127.0.0.1:5001/auth", host: "127.0.0.1:5000"
2024-09-13 17:00:09.857015314  2024/09/13 19:00:09 [error] 175#175: *12 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"
2024-09-13 17:00:14.884535854  2024/09/13 19:00:14 [error] 175#175: *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"
2024-09-13 17:00:14.884540005  2024/09/13 19:00:14 [error] 175#175: *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"

we can’t see the whole config file, (if you post here, please remove passwords) but seems there is a problem with authentication. I recommend checking the video stream using VLC first, then moving to frigate with the correct indentation and syntax. Good luck!

look at the indentation here, it is still wrong. Please compare with the docs example

should be

cameras: 
  eingang: # annkec800
    ffmpeg:

I change but no success:

    cameras: 
  eingang: # annkec800
    ffmpeg:
      output_args:
        record: -f segment -segment_time 10 -segment_format mp4 -reset_timestamps 1 -strftime 1 -c:v copy -tag:v hvc1 -bsf:v hevc_mp4toannexb -c:a aac
        
      inputs:
        - path: rtsp://url
          roles:
            - detect
            - record 

    detect:
      width: 1080
      height: 720

log:

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-fdholder successfully started
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
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 go2rtc-healthcheck successfully started
s6-rc: info: service frigate successfully started
s6-rc: info: service nginx: starting
2024-09-15 06:39:40.934224029  [INFO] Preparing Frigate...
2024-09-15 06:39:40.936478510  [INFO] Starting NGINX...
2024-09-15 06:39:40.937537295  [INFO] Preparing new go2rtc config...
2024-09-15 06:39:40.950920975  [INFO] Starting Frigate...
2024-09-15 06:39:40.954645647  [INFO] No TLS certificate found. Generating a self signed certificate...
2024-09-15 06:39:40.993205450  [INFO] Got IP address from supervisor: 192.168.178.64
2024-09-15 06:39:41.039377230  [INFO] Got WebRTC port from supervisor: 8550
2024-09-15 06:39:41.551846573  [INFO] Starting go2rtc...
2024-09-15 06:39:41.752168168  08:39:41.750 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2
2024-09-15 06:39:41.752172615  08:39:41.750 INF config path=/dev/shm/go2rtc.yaml
2024-09-15 06:39:41.752174373  08:39:41.751 INF [api] listen addr=:1984
2024-09-15 06:39:41.752176300  08:39:41.751 INF [rtsp] listen addr=:8554
2024-09-15 06:39:41.752177973  08:39:41.751 INF [webrtc] listen addr=:8555/tcp
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
2024-09-15 06:39:42.332180458  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2024-09-15 06:39:42.436103153  127.0.0.1 - - [15/Sep/2024:08:39:42 +0200] "" 400 0 "-" "-" "-"
2024-09-15 06:39:43.129932453  [2024-09-15 08:39:43] frigate.app                    INFO    : Starting Frigate (0.14.1-f4f3cfa)
2024-09-15 06:39:43.130558413  [2024-09-15 08:39:43] frigate.app                    INFO    : Creating directory: /tmp/cache
2024-09-15 06:39:43.130922240  [2024-09-15 08:39:43] frigate.util.config            INFO    : Checking if frigate config needs migration...
2024-09-15 06:39:43.150614406  [2024-09-15 08:39:43] frigate.util.config            INFO    : frigate config does not need migration...
2024-09-15 06:39:43.154114165  *************************************************************
2024-09-15 06:39:43.154116930  *************************************************************
2024-09-15 06:39:43.154120671  ***    Your config file is not valid!                     ***
2024-09-15 06:39:43.154122680  ***    Please check the docs at                           ***
2024-09-15 06:39:43.154123992  ***    https://docs.frigate.video/configuration/index     ***
2024-09-15 06:39:43.154160889  *************************************************************
2024-09-15 06:39:43.154162308  *************************************************************
2024-09-15 06:39:43.154163997  ***    Config Validation Errors                           ***
2024-09-15 06:39:43.154165277  *************************************************************
2024-09-15 06:39:43.154737754  objects.filters.cameras: Input should be a valid dictionary or instance of FilterConfig
2024-09-15 06:39:43.154739781  objects.eingang: Extra inputs are not permitted
2024-09-15 06:39:43.154740847  cameras: Field required
2024-09-15 06:39:43.154742005  *************************************************************
2024-09-15 06:39:43.154743184  ***    End Config Validation Errors                       ***
2024-09-15 06:39:43.154744369  *************************************************************
2024-09-15 06:39:44.378990284  [INFO] Service Frigate exited with code 1 (by signal 0)
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
2024-09-15 06:39:44.391326052  [INFO] The go2rtc-healthcheck service exited with code 256 (by signal 15)
2024-09-15 06:39:44.391654108  [INFO] Service CERTSYNC exited with code 256 (by signal 15)
s6-rc: info: service go2rtc-healthcheck successfully stopped
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
2024-09-15 06:39:44.412639041  [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
2024-09-15 06:39:44.416708206  exit with signal: terminated
s6-rc: info: service nginx-log successfully stopped
s6-rc: info: service frigate-log successfully stopped
2024-09-15 06:39:44.422050864  [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