@NickM-27 commented on GitHub (May 1, 2024):
the missing / does not cause any actual issue
@lowlyocean commented on GitHub (May 3, 2024):
Do we know what's actually printing that "connection refused" line? has anyone been able to trace it to a specific line of code?
@lowlyocean commented on GitHub (May 3, 2024):
Thanks. So it would only be printed if I have a browser tab open to some frigate page? Or is there some headless request being made?
@NickM-27 commented on GitHub (May 3, 2024):
the frigate integration as well as other services make requests
@lilp69 commented on GitHub (May 3, 2024):
I've solved my issue by upgrading my hardware from RPI3 to RPI5.
@prmfeddema commented on GitHub (Apr 18, 2024):
Ok - will do. In any case thanks for the prompt feedback. Highly appreciated
@Strux-DK commented on GitHub (Apr 22, 2024):
Hi, I'm experiencing the same behavior, even when changing my config file to the minimal configuration as recommended in the docs. This is the logs…
@milaniez commented on GitHub (May 1, 2024):
Facing the same issue on tag 0.13.2.
one clue is that the url that I see in the error seems to have a type meaning that it is missing a /…
@NickM-27 commented on GitHub (Apr 18, 2024):
you should make your own support issue
@prmfeddema commented on GitHub (Apr 18, 2024):
Same issue here - but Frigate starts and when looking at the logs there is shows that nginx is having these errors:
@prmfeddema commented on GitHub (Apr 18, 2024):
And add to that (from frigate log)
2024-04-18 21:23:33.214991217 [2024-04-18 23:23:33] frigate.app INFO : Capture process…
@NickM-27 commented on GitHub (Apr 18, 2024):
that is very normal and not an issue, frigate is not started yet so the connection is refused then it starts working
your second set of logs is…
@prmfeddema commented on GitHub (Apr 18, 2024):
Thanks - looking into the MQTT log i see this:
s6-rc: info: service s6rc-oneshot-runner: starting s6-rc: info: service s6rc-oneshot-runner…
@prmfeddema commented on GitHub (Apr 18, 2024):
Frigate has started (high CPU though). last lines of the log show (just the last 2 lines)
2024-04-18 21:42:39.829136915 [2024-04-18 23:42:39]…