#Frigate 404 error accessing go2rtc restream

1 messages · Page 1 of 1 (latest)

bright plank
#

I'm trying to connect frigate to my Amcrest IP4M-1041W. I have frigate running in Proxmox using the helper script from https://community-scripts.github.io/ProxmoxVE/scripts?id=frigate.

If I configure the camera in Frigate to pull directly from the rtsp url, it streams properly. However, when I try to use go2rtc, it no longer works. I've tried with and without the ffmpeg prefix.

I noticed that no streams show up in the go2rtc GUI or API, which seems like the issue. The Frigate logs show an error: rtsp://127.0.0.1:8554/living_room: Server returned 404 Not Found. However, the go2rtc logs don't show any errors or logs at all besides the startup info logs. This is all under the assumption that I should be seeing the streams in go2rtc.

mqtt:
  enabled: false

logger:
  default: debug

ffmpeg:
  hwaccel_args: preset-vaapi

go2rtc:
  log:
    exec: trace
  streams:
    living_room:
      - ffmpeg:rtsp://<username>:<password>@192.168.8.237:554/cam/realmonitor?channel=1&subtype=0

cameras:
  living_room:
    ffmpeg:
      inputs:
        - path: rtsp://127.0.0.1:8554/living_room
          input_args: preset-rtsp-restream

version: 0.14
tls:
  enabled: false

The go2rtc /api/streams returns {}. I'm attaching the go2rtc log file. Let me know if there are any other diagnostics I c an provide to help narrow it down. Any help/suggestions would be appreciated!

#

Frigate 404 error accessing go2rtc restream

crystal gate
#

from someone who spent ages trying to solve problems a couple of weeks ago... that script is outdated and installs an outdated version of frigate and has some other issues.

i suggest you install a docker LXC with https://community-scripts.github.io/ProxmoxVE/scripts?id=docker
enabling priviledged mode
then installing frigate within onto the docker on that LXC. (e.g. with docker compose)
this solved alot of problems for me

#

also: this does also seem more like a frigate issue then a HA one?

bright plank
#

this is 100% a frigate issue, Im sure I could have opened a github issue or something similar but some frigate issues directed me towards this channel -- that's super helpful to know! I will try that out ASAP