For questions, make sure to go through the docs first, they're very well put together. http://docs.frigate.video/guides/getting_started
Setup getting stuck at go2rtc healthcheck
I am able to access my docker container via portainer, but not able to access the Frigate dashboard on the same IP at the proper port. Everything in my logs looks good until I get to go2rtc healthcheck. After that it just repeats what appears to be a messed HTTP request. Any idea what the request source might be?
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 frigate-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 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-11-29 23:09:40.493034331 [INFO] Preparing Frigate... 2024-11-29 23:09:40.494727741 [INFO] Preparing new go2rtc config... 2024-11-29 23:09:40.501316621 [INFO] Starting NGINX... 2024-11-29 23:09:40.504703940 [INFO] Starting Frigate... 2024-11-29 23:09:40.820534457 [INFO] Starting go2rtc... 2024-11-29 23:09:40.934754190 23:09:40.934 INF go2rtc platform=linux/amd64 revision=b2399f3 version=1.9.2 2024-11-29 23:09:40.936455129 23:09:40.936 INF config path=/dev/shm/go2rtc.yaml 2024-11-29 23:09:40.937214738 23:09:40.937 INF [api] listen addr=:1984 2024-11-29 23:09:40.937906486 23:09:40.937 INF [rtsp] listen addr=:8554 2024-11-29 23:09:40.938252372 23:09:40.938 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-11-29 23:09:41.628266109 [INFO] Starting certsync... s6-rc: info: service legacy-services successfully started 2024-11-29 23:09:41.757705163 127.0.0.1 - - [29/Nov/2024:23:09:41 -0500] "" 400 0 "-" "-" "-" 2024-11-29 23:09:41.922299450 [2024-11-29 23:09:41] frigate.app INFO : Starting Frigate (0.14.1-f4f3cfa) 2024-11-29 23:09:41.922903190 [2024-11-29 23:09:41] frigate.util.config INFO : Checking if frigate config needs migration... 2024-11-29 23:09:41.932964952 [2024-11-29 23:09:41] frigate.util.config INFO : frigate config does not need migration... 2024-11-29 23:09:41.964800246 [2024-11-29 23:09:41] peewee_migrate.logs INFO : Starting migrations 2024-11-29 23:09:41.965722473 [2024-11-29 23:09:41] peewee_migrate.logs INFO : There is nothing to migrate 2024-11-29 23:09:41.970739215 [2024-11-29 23:09:41] frigate.app INFO : Recording process started: 332 2024-11-29 23:09:41.984367472 [2024-11-29 23:09:41] frigate.app INFO : Recording process started: 334 2024-11-29 23:09:41.984371729 [2024-11-29 23:09:41] frigate.app INFO : go2rtc process pid: 108 2024-11-29 23:09:42.008036673 [2024-11-29 23:09:42] frigate.app INFO : Output process started: 362 2024-11-29 23:09:42.029371075 [2024-11-29 23:09:42] frigate.app INFO : Camera processor started for FrontCam: 380 2024-11-29 23:09:42.046657638 [2024-11-29 23:09:42] frigate.app INFO : Capture process started for FrontCam: 386 2024-11-29 23:09:44.622859316 [2024-11-29 23:09:42] detector.coral INFO : Starting detection process: 361 2024-11-29 23:09:44.623406993 [2024-11-29 23:09:42] frigate.detectors.plugins.edgetpu_tfl INFO : Attempting to load TPU as usb 2024-11-29 23:09:44.626243867 [2024-11-29 23:09:44] frigate.detectors.plugins.edgetpu_tfl INFO : TPU found 2024-11-29 23:09:50.490294895 [INFO] Starting go2rtc healthcheck service... 2024-11-29 23:10:41.781369066 127.0.0.1 - - [29/Nov/2024:23:10:41 -0500] "" 400 0 "-" "-" "-" 2024-11-29 23:11:41.806054308 127.0.0.1 - - [29/Nov/2024:23:11:41 -0500] "" 400 0 "-" "-" "-" 2024-11-29 23:12:41.829416352 127.0.0.1 - - [29/Nov/2024:23:12:41 -0500] "" 400 0 "-" "-" "-" 2024-11-29 23:13:41.850599674 127.0.0.1 - - [29/Nov/2024:23:13:41 -0500] "" 400 0 "-" "-" "-"
Sort by:
Best
Open comment sort options
Best
Top
New
Controversial
Old
Q&A
These localhost 400's are of no concern.
That's good to hear. I am unable to navigate to the frigate dashboard though. Any idea how I can better logs as to why? I've double checked the port is correct, and I can access the docker container via portainer on the same URL at its own port.