Adding new cameras, had issues, so thought to clean up startup before I tackle the cameras again #15700
-
I was in the process of adding a new Reolink E1 Pro to my setup. I already have another but it seems that the firmware on this one presents a bunch of new options that didn't exist on the older one. I couldn't get it working (yet) so decided to step back and remove it from the config and clean-up my startup errors before going back to adding the camera. I see these errors and was hoping I could get some insights on them? Thanks. 2024-12-27 13:03:04.156256791 2024/12/27 13:03:04 [error] 160#160: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.54, server: , request: "GET /ws HTTP/1.1", subrequest: "/auth", upstream: "http://127.0.0.1:5001/auth", host: "192.168.2.110:5000" .110 is my Unraid server running Frigate and 2024-12-27 13:03:04.335350102 13:03:04.335 WRN [app] read config error="yaml: unmarshal errors:\n line 57: cannot unmarshal !!seq into string" I see this error in my GO2RTC log (at bottom of post)? and 2024-12-27 13:03:05.073929238 2024/12/27 13:03:05 [error] 161#161: *4 auth request unexpected status: 502 while sending to client, client: 192.168.2.113, server: , request: "GET /api/stats HTTP/1.1", host: "192.168.2.110:5000" .113 is my home assistant Here is my config:
|
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 2 replies
-
Your go2rtc config is incorrect. Try removing the
The |
Beta Was this translation helpful? Give feedback.
Those are expected and not of any concern. They are from your browser trying to access Frigate's API and websocket before Frigate has fully started.