Getting a 500 HTTP error on http://frigate:5000 site when I click a camera to see full size go2rtc view?

[Sarah-Connelli]

This has made me go round and round in circles.

I set up a go2rtc stream for a camera in the config, and I can see this rtsp stream via VLC, however it doesn't work in the frigate management site.

I opened the developer-console and I saw the following error:

GET http://localip:5000/api/go2rtc/streams/Hill 500 (INTERNAL SERVER ERROR)

PS... the go2rtc stream is being recorded just fine by Frigate, so the linkage is there as far as go2rtc is concerned.

Does anyone have any ideas?

Info:
I'm on version 0.14.1.
Frigate is running inside a Docker container, with 'HOST' networking enabled.
Everything else is working great, just the go2rtc functionality is broken my end because of these API 500 errors.

[NickM-27]

This is the code in 0.14:

    r = requests.get(
        f"http://127.0.0.1:1984/api/streams?src={camera_name}&video=all&audio=all&microphone"
    )
    if not r.ok:
        logger.error("Failed to fetch streams from go2rtc")
        return make_response(
            jsonify({"success": False, "message": "Error fetching stream data"}),
            500,
        )
    stream_data = r.json()
    for producer in stream_data.get("producers", []):
        producer["url"] = clean_camera_user_pass(producer.get("url", ""))
    return jsonify(stream_data)

so presumably go2rtc is returning an error when the probe call is used. Can you confirm you are not using a custom version of go2rtc?

[NickM-27]

You can also try running the call yourself and see what go2rtc returns curl http://127.0.0.1:1984/api/streams?src=Hill&video=all&audio=all&microphone

[Sarah-Connelli]

Ahhh, so the API port '1984' is actually hardcoded?

In the config file, I changed the ports because I do have another go2rtc installation running on the standard ports, I assumed because you can configure the ports in the config yaml file then everything should just tie up nicely?

go2rtc:
  api:
    listen: :9984
  streams:
    Hill:
      - rtsp://admin:{FRIGATE_RPASS}@localip:554/Streaming/Channels/101

  rtsp:
    listen: :9554

  srtp:
    listen: :9443

  webrtc:
    listen: :9555

Should the config file ports be respected instead of being hardcoded?

As I take it that the Frigate system builds the go2rtc config file using the go2rtc: section from Frigate's main configuration file.

The user documentation says:

# Optional: Restream configuration
# Uses https://github.com/AlexxIT/go2rtc (v1.9.2)
go2rtc:

...and I did follow through to that 'AlexxIT' link and used the configuration info there to guide me, hence presuming the ports are changeable as well as defining streams.

[hawkeye217]

The Frigate backend assumes the internal go2rtc is running on port 1984 throughout its codebase: https://github.com/search?q=repo%3Ablakeblackshear%2Ffrigate%201984&type=code

The recommended setup method is to use port mapping with Docker rather than host networking where you can map external ports to the container's port 1984.

[Sarah-Connelli]

The Frigate backend assumes the internal go2rtc is running on port 1984 throughout its codebase: https://github.com/search?q=repo%3Ablakeblackshear%2Ffrigate%201984&type=code

The recommended setup method is to use port mapping with Docker rather than host networking where you can map external ports to the container's port 1984.

If that is the way that has been decided then I just have to live with it I guess, however it didn't say as much in the doco so I assumed Frigate's go2rtc can be as configurable as an external go2rtc service.

One concern is that the problem I see with this is that it is very limiting to rely upon a Docker install if one did not want to run in Docker, I personally do feel that go2rtc's port config should be respected to make things flexible - unless Docker is the only way Frigate is to be supported.

PS I tend to avoid using Docker's port translation with a multitude of bridges when all the services are going to be talking to each other, but that is just a personal tendency as I find it easier to manage and firewall things via iptables without a tonne load of pesky linux bridges getting in the way.

[NickM-27]

Do you have a recommendation of place in the docs where you would search for this? There is no direct go2rtc main page, and I imagine a user who would typically be changing ports may not need or check Configuring go2rtc so I am not sure where such a warning would fit, perhaps Installation near the ports definitions?

[Sarah-Connelli]

I'd suggest putting a comment in the actual "Full Reference Configuration":

Please add to the comment already there under the link out to AlexIT's github, something to the effect of "#Please note the GO2RTC ports should not be changed as they are hardcoded to defaults inside Frigate's codebase"

In the ideal world the API port can just be picked up and used dynamically from the config as it is only referenced in 5 lines of code as per Github repo scan - but from the replies thus far, it seems the design choice for go2rtc hardcoded ports is perpetual.

[NickM-27]

Right, I think in your case that is reasonable, in general what we want to avoid is cases where users only intend to run an external go2rtc instance as that is not supported if the full feature set is desired. I will put up a PR to update the documentation, thank you for the suggestion.

#16013