PatSloan
PatSloan
``` 2024-01-11 21:59:37.734107695 [INFO] Preparing Frigate... 2024-01-11 21:59:37.743286242 [INFO] Starting Frigate... 2024-01-11 21:59:40.286228759 [2024-01-11 21:59:40] frigate.app INFO : Starting Frigate (0.13.0-49814b3) 2024-01-11 21:59:40.340431122 [2024-01-11 21:59:40] peewee_migrate.logs INFO : Starting migrations...
192.168.2.1 is my router/firewall/dns. why is that showing in the logs?
``` 2024-01-12 10:26:51.054688989 [INFO] Starting NGINX... 2024-01-12 10:26:51.521340993 2024/01/12 10:26:51 [error] 144#144: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 192.168.2.1, server: , request: "GET /ws HTTP/1.1",...
``` 2024-01-12 10:26:51.053677949 [INFO] Preparing Frigate... 2024-01-12 10:26:51.062704775 [INFO] Starting Frigate... 2024-01-12 10:26:52.422709094 [2024-01-12 10:26:52] frigate.app INFO : Starting Frigate (0.13.0-49814b3) 2024-01-12 10:26:52.482440706 [2024-01-12 10:26:52] peewee_migrate.logs INFO : Starting migrations...
Sorry, thought i was using the formatting propper. new logs above. this is an upgrade from prod release to 13 beta 6 to 13 rc1 Accessing it via local network....
frigate docker compose: ```yaml version: "3.9" services: frigate: container_name: frigate_beta privileged: true # this may not be necessary for all setups restart: unless-stopped image: ghcr.io/blakeblackshear/frigate:0.13.0-rc1 cap_add: - CAP_PERFMON # image:...
Yes i can access http://192.168.2.6:5000/ just fine I don't know how long those errors were being raised. i am very new to frigate so am sort of pealing the onion...
> what are the frigate logs? Any other guidance? been googling all day with no luck :(
HAOS is on a vm using virtualbox on ubuntu. frigate is running in a separate docker instance on the same ubuntu machine. one detail is they are on two subnets....
This is just an update. Still a problem after updating to frigate 13.1 and hacs frigate integration 5.0 Any thoughts on a solution? @NickM-27 ??