go2rtc icon indicating copy to clipboard operation
go2rtc copied to clipboard

Config reverting to default

Open amoussa1229 opened this issue 1 year ago • 6 comments

I have my go2rtc config setup and both it and Frigate are working well (I know this isn't the Frigate repo lol).

Whenever I have to shut down or reboot the machine, the go2rtc config reverts back to the default.

I apologize if there is any info I forgot to add, this is my first time posting on GitHub

Here's my go2rtc logs if needed

6:54:53.160 PM | info | go2rtc version=1.9.4 platform=linux/amd64 revision=a4885c2 6:54:53.160 PM | info | config path=/dev/shm/go2rtc.yaml 6:54:53.161 PM | info | [api] listen addr=:1984 6:54:53.161 PM | info | [rtsp] listen addr=:8554 6:54:53.162 PM | info | [webrtc] listen addr=:8555/tcp

amoussa1229 avatar Aug 14 '24 23:08 amoussa1229

This config created by Frigate.

AlexxIT avatar Aug 15 '24 03:08 AlexxIT

This config created by Frigate.

This wasn't. This was created myself and added, frigate would not add it automatically while i was setting up

amoussa1229 avatar Aug 15 '24 04:08 amoussa1229

This config path=/dev/shm/go2rtc.yaml

AlexxIT avatar Aug 15 '24 05:08 AlexxIT

to persist your go2rtc.yaml in your frigate container you must add your go2rtc config statements to the config.yaml from frigate as described in the documentation

do not edit the config via IP:1984 and make changes in the config there. you can only change them there temporarily.

if this then works, you have to transfer it to the config.yaml of frigate

b2un0 avatar Aug 21 '24 12:08 b2un0

so this interface on IP:1984 is only to check connections?

tojapawel avatar Nov 09 '24 00:11 tojapawel

so this interface on IP:1984 is only to check connections?

only if you using the shipped version from frigate.

thats the reason, why im using go2rtc as standalone docker container ;)

b2un0 avatar Nov 12 '24 10:11 b2un0