Do I Need a go2rtc restream to connect to remote go2rtc service?

[moogoos]

I tried asking in AI and didn't get my answer exactly. Instead of configuring a restream, can I configure the cameras to connect directly to the remote go2rtc service? I am trying that and get a 401. so not sure how to setup auth if i'm not connecting to a local restream config.

[inkeep-ai-assistant[bot]]

(1)

Based on the available sources, you do not necessarily need a local go2rtc restream to connect cameras to a remote go2rtc service. The documentation shows that go2rtc streams can be configured with various source types, not just local RTSP streams (1).

However, the sources don't provide specific information about authentication methods for connecting to remote go2rtc services or how to handle 401 authentication errors when connecting directly to external go2rtc instances.

The documentation shows that go2rtc supports many different stream types (1), and you can configure cameras to use external sources. For example, the configuration shows streams can reference external RTSP URLs:

go2rtc:
  streams:
    back:
      - rtsp://user:password@10.0.10.10:554/cam/realmonitor?channel=1&subtype=2

(1)

But the sources don't contain specific guidance on remote go2rtc service authentication or troubleshooting 401 errors for external go2rtc connections.

For authentication setup with remote go2rtc services, you might want to check the go2rtc documentation directly or visit GitHub for more specific guidance on this configuration scenario.

📚 Sources:

1. Configuring go2rtc

---

Have another question? Just tag @inkeep.

[hawkeye217]

You're free to use an external go2rtc instance for the URLs in your camera config, but know that you will lose the benefits of the much improved live view that using the internal go2rtc provides.

[moogoos]

mmhmmm. definitely don't want to lose that. how does auth work then to a remote go2rtc service? Curious. How do I pass creds? Cause it seems, for the cameras that hit the local go2rtc there is no password/user being passed so not sure how that works. it's all set in the go2rtc

[hawkeye217]

Not sure where the 401 is coming from, go2rtc streams can be accessed without authorization: https://github.com/AlexxIT/go2rtc?tab=readme-ov-file#security

[moogoos]

In my original go2rtc config that I pull from the cameras on I set:

go2rtc:
  rtsp:
    username: user
    password: pdub

which works fine for the local cameras on that same config to access locally with 127.0.0.1:8554...

but when i try to connect to 8554 from the second frigate config referencing the domain in the config where the go2rtc stream is I get:

method OPTIONS failed: 401 Unauthorized

when I disable the source stream go2rtc config with no user and password the remote frigate instance will work then and not get the 401. So not sure how to pass auth in the camera url. Haven't tried the username:password@cameradomain though so mayve that works.

[hawkeye217]

I'd recommend reaching out on go2rtc's repo if you need further help.

Just know that your live views in Frigate will be limited to 5fps jsmpeg if you don't use the internal go2rtc.

[moogoos]

fair enough. always appreciate the help.

[NickM-27]

You enabled auth on the go2rtc service, so from Frigate you need to set the username and password