Latest update for rtsp/go2rtc selects wrong IP?

[ronbruins]

With the latest update the live stream can be chosen. However the go2rtc stream, as per frigate documentation, can be set to 127.0.0.1:8554' Viewu uses this url for the go2rtc stream, instead it should use the IP of the frigate server/camera

so instead of: rtsp://127.0.0.1:8554/voordeur It should use (in my case): rtsp://192.168.1.171:8554/voordeur

[ronbruins]

I have updated my frigate config to use the servers native IP instead of 127.0.0.1 now the go2rtc works.

However: seems you made a mistake with the buttons. go2rtc shows my rtsp feeds and the other way around :-)

[mjehrhart]

Thanks for pointing out that mixed up the two streams in the settings =). I'll take a look at that.

So are you saying I need to replace localhost with the frigate server IP for go2rtc streams? I may have been doing it wrong in my config as I manually replace localhost with my frigate server. Is that wrong to do? I need to clarify so I make the right changes.

Big thanks to you testing and posting this. It helps all of us out.

[ronbruins]

Well you don't need to change it, however it could be a good thing to do. Frigate documentation states to use localhost(127.0.0.1) as the IP for the camera coming from go2rtc, but of course go2rtc also streams the feeds through the actual IP of the go2rtc(frigate) server.

So there are 2 ways to approach this:

• if you see the go2rtc stream contains localhost/127.0.0.1 replace it with the frigate server IP
• Make a documentation note, tat to use go2rtc people have to use that IP for their camera stream in frigate.

It doesn't really matter, the only (dis)advantage is that when moving frigate to another server will be easier when using localhost as the IP could change.

[ronbruins]

here the link where the config examples are

https://docs.frigate.video/configuration/camera_specific

[mjehrhart]

You are right. I totally mixed them up and now I remember how and why I did it. I’ll fix it for the next update.

[mjehrhart]

This solution is in Build(20) which is now released on TestFlight