[Config Support]: #20740

dougransom · 2025-10-31T15:10:50Z

dougransom
Oct 31, 2025

Describe the problem you are having

Concerning errors in log. What should I do with this information?

Will these errors createa problem with mqtt?

Version

0.16.2

Frigate config file

# yaml-language-server: $schema=http://ha.local:5000/api/config/schema.json
detectors:
  coral:
    type: edgetpu
    device: usb
objects:
  track:
    - person
    - car
    - motorcycle
    - bus
    - cat
    - dog
    - horse
    - sheep
    - cow

record:
  enabled: true
mqtt:
  # Required host name
  host: ha
  port: 1883
  #topic prefix must be  unique if running multiple instances
  topic_prefix: frigate
  stats_interval: 60
  user: mqttuser
  password: hotdog
environment_vars:
  LIBVA_DRIVER_NAME: i965

go2rtc:
  streams:
  
    garage1_cam_rec: 
      - rtsp://underdoug:[email protected]:554/stream1
      
    garage1_cam_det:
      - rtsp://underdoug:[email protected]:554/stream2

  
  # https://www.reddit.com/r/frigate_nvr/comments/1dkd2ua/doorbell_exceeded_fps_limit_exiting_ffmpeg/
  #possibly need to change settings on doorbell to use flv
    reolink_doorbell_det:
      - rtsp://doug:[email protected]:554/h264Preview_01_sub

    reolink_doorbell_rec:
      - rtsp://doug:[email protected]:554/h264Preview_01_main


# Optional: logger verbosity settings
logger:
  # Optional: Default log verbosity (default: shown below)
  default: info
  # Optional: Component specific logger overrides
  logs:
    frigate.event: debug

ffmpeg:
  hwaccel_args: preset-intel-qsv-h264

audio:
  enabled: true

cameras:
  garage_cam1:
    ffmpeg:
      inputs:
        - path: rtsp://localhost:8554/garage1_cam_det
          roles:
            - detect
            - audio
          input_args: preset-rtsp-restream
        - path: rtsp://localhost:8554/garage1_cam_rec
          roles:
            - record
          input_args: preset-rtsp-restream
    audio:
      enabled: true
      listen:
        - cat
    detect:
      enabled: true # <---- disable detection until you have a working camera feed
      # width:   # <---- update for your camera's resolution
      # height:   # <---- update for your camera's resolution
    record:
      enabled: true
      retain:
        mode: motion
    snapshots:
      enabled: true

  reolink_doorbell_det:
    motion:
      mask:
        - 0.461,0.507,0.465,0.543,0.618,0.536,0.612,0.506
        - 0.333,-0.001,0.333,0.056,0.662,0.056,0.66,0
    ffmpeg:
      inputs:
        - path: rtsp://localhost:8554/reolink_doorbell_det
          roles:
            - detect
            - audio
          input_args: preset-rtsp-restream
        - path: rtsp://localhost:8554/reolink_doorbell_rec
          roles:
            - record
          input_args: preset-rtsp-restream
    audio:
      enabled: true
      listen:
        - cat
    detect:
      enabled: true # <---- disable detection until you have a working camera feed
      # width: 640 # <---- update for your camera's resolution
      # height: 480 # <---- update for your camera's resolution
    record:
      enabled: true
    snapshots:
      enabled: true


    zones:
      default_zone:
        coordinates: 
          0.307,0.103,0.359,0.48,0.34,0.615,0.209,0.597,0.198,0.979,0.959,0.987,0.949,0.585,0.853,0.569,0.824,0.156,0.534,0.075
        loitering_time: 0
birdseye:
  enabled: true
  mode: continuous
version: 0.16-0
detect:
  enabled: true

Relevant Frigate log output

2025-10-31 12:40:13.627645649  [INFO] Starting go2rtc...
2025-10-31 12:40:13.737689973  05:40:13.737 INF go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
2025-10-31 12:40:13.737696090  05:40:13.737 INF config path=/dev/shm/go2rtc.yaml
2025-10-31 12:40:13.739104676  05:40:13.738 INF [api] listen addr=:1984
2025-10-31 12:40:13.739109529  05:40:13.738 INF [rtsp] listen addr=:8554
2025-10-31 12:40:13.739838495  05:40:13.739 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-10-31 12:40:15.986632039  [INFO] Starting certsync...
s6-rc: info: service legacy-services successfully started
2025-10-31 12:40:16.525740669  127.0.0.1 - - [31/Oct/2025:05:40:16 -0700] "" 400 0 "-" "-" "-"
2025-10-31 12:40:17.161782493  [2025-10-31 05:40:17] frigate.util.config            INFO    : Checking if frigate config needs migration...
2025-10-31 12:40:17.184224296  [2025-10-31 05:40:17] frigate.util.config            INFO    : frigate config does not need migration...
2025-10-31 12:40:17.572114842  2025/10/31 05:40:17 [error] 213#213: *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-10-31 12:40:17.572136514  2025/10/31 05:40:17 [error] 213#213: *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-10-31 12:40:22.605025970  2025/10/31 05:40:22 [error] 214#214: *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-10-31 12:40:22.605045942  2025/10/31 05:40:22 [error] 214#214: *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-10-31 12:40:22.614467127  [INFO] Starting go2rtc healthcheck service...
2025-10-31 12:40:26.198332279  [2025-10-31 05:40:26] frigate.app                    INFO    : Starting Frigate (0.16.2-4d58206)
2025-10-31 12:40:26.200027649  [2025-10-31 05:40:26] frigate.app                    INFO    : Creating directory: /tmp/cache
2025-10-31 12:40:26.211169740  [2025-10-31 05:40:26] peewee_migrate.logs            INFO    : Starting migrations
2025-10-31 12:40:26.212494922  [2025-10-31 05:40:26] peewee_migrate.logs            INFO    : There is nothing to migrate
2025-10-31 12:40:26.221332143  [2025-10-31 05:40:26] frigate.app                    INFO    : Recording process started: 414
2025-10-31 12:40:26.231208822  [2025-10-31 05:40:26] frigate.app                    INFO    : Review process started: 425
2025-10-31 12:40:26.233421318  [2025-10-31 05:40:26] frigate.app                    INFO    : go2rtc process pid: 125
2025-10-31 12:40:26.249269847  [2025-10-31 05:40:26] detector.coral                 INFO    : Starting detection process: 439
2025-10-31 12:40:26.251563438  [2025-10-31 05:40:26] frigate.detectors.plugins.edgetpu_tfl INFO    : Attempting to load TPU as usb
2025-10-31 12:40:26.261724361  [2025-10-31 05:40:26] frigate.app                    INFO    : Output process started: 459
2025-10-31 12:40:26.343200230  [2025-10-31 05:40:26] frigate.app                    INFO    : Camera processor started for garage_cam1: 480
2025-10-31 12:40:26.343579968  [2025-10-31 05:40:26] frigate.app                    INFO    : Camera processor started for reolink_doorbell_det: 483
2025-10-31 12:40:26.390825864  [2025-10-31 05:40:26] frigate.app                    INFO    : Capture process started for garage_cam1: 495
2025-10-31 12:40:26.437192192  [2025-10-31 05:40:26] frigate.app                    INFO    : Capture process started for reolink_doorbell_det: 511
2025-10-31 12:40:26.453161790  INFO: Created TensorFlow Lite XNNPACK delegate for CPU.
2025-10-31 12:40:26.521748654  [2025-10-31 05:40:26] frigate.audio_manager          INFO    : Audio processor started (pid: 528)
2025-10-31 12:40:26.816077058  [2025-10-31 05:40:26] frigate.api.fastapi_app        INFO    : Starting FastAPI app
2025-10-31 12:40:27.101324492  [2025-10-31 05:40:27] frigate.api.fastapi_app        INFO    : FastAPI started
2025-10-31 12:40:28.859610196  [2025-10-31 05:40:28] frigate.detectors.plugins.edgetpu_tfl INFO    : TPU found

Relevant go2rtc log output

2025-10-31 12:40:13.092714701  [INFO] Preparing new go2rtc config...
2025-10-31 12:40:13.133026983  [INFO] Got IP address from supervisor: 192.168.0.184
2025-10-31 12:40:13.172402610  [INFO] Got WebRTC port from supervisor: 8555
2025-10-31 12:40:13.627645649  [INFO] Starting go2rtc...
2025-10-31 12:40:13.737689973  05:40:13.737 INF go2rtc platform=linux/amd64 revision=fa580c5 version=1.9.9
2025-10-31 12:40:13.737696090  05:40:13.737 INF config path=/dev/shm/go2rtc.yaml
2025-10-31 12:40:13.739104676  05:40:13.738 INF [api] listen addr=:1984
2025-10-31 12:40:13.739109529  05:40:13.738 INF [rtsp] listen addr=:8554
2025-10-31 12:40:13.739838495  05:40:13.739 INF [webrtc] listen addr=:8555
2025-10-31 12:40:22.614467127  [INFO] Starting go2rtc healthcheck service...

Frigate stats

No response

Operating system

Home Assistant OS

Install method

Home Assistant Add-on

docker-compose file or Docker CLI command

Object Detector

Coral

Screenshots of the Frigate UI's System metrics pages

No response

Any other information that may be helpful

No response

2025-10-31T15:12:23Z

inkeep-ai-assistant[bot]
bot Oct 31, 2025

The errors you're seeing are actually not concerning. Let me explain what's happening:

The nginx connection errors

The nginx errors you see:

[error] 213#213: *2 connect() failed (111: Connection refused) while connecting to upstream
[error] 213#213: *2 auth request unexpected status: 502 while sending to client

These occur during Frigate's startup sequence. They appear because nginx is trying to connect to Frigate's API before it's fully initialized(1). This is completely normal and expected behavior during startup(1).

Impact on MQTT

These errors will not create problems with MQTT(2). Your MQTT configuration looks correct with the host, port, user, and password properly set(2). The nginx errors are unrelated to MQTT functionality(2).

What you should do

Nothing. These are expected startup messages and don't indicate any problem with your system(1). Once Frigate finishes starting up (which your logs show it did successfully with "FastAPI started"), everything operates normally(1).

Your Frigate instance started successfully as indicated by:

Detection process started
Camera processors started for both cameras
Audio processor started
FastAPI started

All systems are functioning correctly.

📚 Sources:

Have another question? Just tag @inkeep.

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

Uh oh!

[Config Support]: #20740

Uh oh!

{{title}}

Uh oh!

Replies: 1 comment

Uh oh!

{{title}}

Uh oh!

Select a reply

Uh oh!

Uh oh!

[Config Support]: #20740

Uh oh!

dougransom Oct 31, 2025

Describe the problem you are having

Version

Frigate config file

Relevant Frigate log output

Relevant go2rtc log output

Frigate stats

Operating system

Install method

docker-compose file or Docker CLI command

Object Detector

Screenshots of the Frigate UI's System metrics pages

Any other information that may be helpful

Replies: 1 comment

Uh oh!

inkeep-ai-assistant[bot] bot Oct 31, 2025

The nginx connection errors

Impact on MQTT

What you should do

dougransom
Oct 31, 2025

inkeep-ai-assistant[bot]
bot Oct 31, 2025