search

blakeblackshear / frigate-hass-addons

Frigate hass.io addons
MIT License
250 stars 134 forks source link

Frigate Proxy Configuration? #48

Open mkelley88 opened 3 years ago

mkelley88 commented 3 years ago

Hello, I am running Frigate on TrueNAS SCALE in it's own container and I don't understand how to configure the Home Assistant "Frigate Proxy" add-on to direct it to my external Frigate instance.

I have installed the add-on, started it, and clicked on "Frigate Proxy" in the sidebar, but I get nothing but a blank page. If I don't start it first, I get a message saying it isn't started. I can't seem to find any instructions on how to get this working.

The link in [Home Assistant]->[Supervisor]->[Frigate NVR Proxy] that says "Visit the Frigate NVR Proxy page for more details" simply takes me to the main Frigate github "https://github.com/blakeblackshear/frigate".

The readme.md provided here "https://github.com/blakeblackshear/frigate-hass-addons/tree/main/frigate_proxy" is also not super helpful.

I hope I have provided enough information to help understand my issue. Frigate is a great project and I can't wait to watch it grow. Thanks!

blakeblackshear commented 3 years ago

You should see a Configuration tab in Home Assistant after installing the addon. You just need to specify the ip:port of frigate there.

p3ck commented 2 years ago

This is the output from the configuration tab:

image

This is the version I have installed: image

Floriszz commented 1 year ago

Mine does show the Configuration page. When I fill in the IP and port of the Frigate WebUI, the logs show me the following. (see below) Clicking on 'Frigate' in the sidebar, I get: 502 bad gateway.(se screenshot below) Of course pasting this Frigate URL with port in another browser tab serves me the Frigate webinterface nicely. What to do next?

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 00-banner.sh: executing... 
-----------------------------------------------------------
 Add-on: Frigate Proxy
 Proxy addon for Frigate
-----------------------------------------------------------
 Add-on version: 1.3
 You are running the latest version of this add-on.
 System: Home Assistant OS 9.5  (aarch64 / raspberrypi3-64)
 Home Assistant Core: 2023.2.1
 Home Assistant Supervisor: 2023.01.1
-----------------------------------------------------------
 Please, share the above information when looking for help
 or support in, e.g., GitHub, forums or the Discord chat.
-----------------------------------------------------------
[cont-init.d] 00-banner.sh: exited 0.
[cont-init.d] 01-log-level.sh: executing... 
[cont-init.d] 01-log-level.sh: exited 0.
[cont-init.d] nginx.sh: executing... 
[cont-init.d] nginx.sh: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
[20:37:24] INFO: Starting NGinx...
nginx: [emerg] invalid host in upstream "http://192.168.1.22:5055" in /etc/nginx/includes/upstream.conf:2
[20:37:25] INFO: Starting NGinx...
nginx: [emerg] invalid host in upstream "http://192.168.1.22:5055" in /etc/nginx/includes/upstream.conf:2

image

image

Floriszz commented 1 year ago

The answer is that the server must be entered without the 'http://'. So in my case it should be: 192.168.1.22:5055 The documentation tab clearly explains it. But if you copy the server ip with port number from the browser address bar in Google Chrome, although it does not show the 'http://' part, it will copy and paste it!