looks like you need to enable the port 5000, it is not enabled
1 Like
Hi, how does one do this? Thank you.
Late 2023 I am still getting this message: āFailed to connectā.
same here, tried down grading etc but nothing worked
Like many of the others here, I kept getting the failed to connect error even though Frigate was accessible from the same URL. On a lark, I changed it to http://localhost:5000 which worked for me!
Context: Frigate is running on docker. Home assistant is also running on docker on the same machine. Frigate is in bridge networking, while home assistant has host networking. Iām not sure why putting the server IP would cause it to fail, but Iām glad localhost worked for me.
I have been struggling with that hostname issue for so long. Why it isnāt explained better or more predominantly, I donāt know.
I got proxy working fine when Frigate as HASS add-on. However when Frigate runs in add-on there is no way to control where media directory is.
So I created docker container for Frigate and add to HASS using integration. Integration works.
But proxy does not!!
Add-on: Frigate Proxy
Proxy addon for Frigate
-----------------------------------------------------------
Add-on version: 1.5
You are running the latest version of this add-on.
System: Debian GNU/Linux 12 (bookworm) (amd64 / qemux86-64)
Home Assistant Core: 2024.7.4
Home Assistant Supervisor: 2024.08.0
-----------------------------------------------------------
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.
[22:14:44] INFO: Starting NGinx...
2024/08/07 22:14:46 [error] 348#348: *3 access forbidden by rule, client: 127.0.0.1, server: 69f7f093-frigate-proxy, request: "GET // HTTP/1.1", host: "hpdebian:8123", referrer: "http://hpdebian:8123/hassio/addon/69f7f093_frigate-proxy"
2024/08/07 22:14:48 [error] 348#348: *5 access forbidden by rule, client: 127.0.0.1, server: 69f7f093-frigate-proxy, request: "GET // HTTP/1.1", host: "hpdebian:8123", referrer: "http://hpdebian:8123/69f7f093_frigate-proxy"
2024/08/07 22:14:51 [error] 348#348: *7 access forbidden by rule, client: 127.0.0.1, server: 69f7f093-frigate-proxy, request: "GET // HTTP/1.1", host: "hpdebian:8123", referrer: "http://hpdebian:8123/69f7f093_frigate-proxy/ingress"
2024/08/07 22:14:56 [error] 348#348: *9 access forbidden by rule, client: 127.0.0.1, server: 69f7f093-frigate-proxy, request: "GET // HTTP/1.1", host: "hpdebian:8123", referrer: "http://hpdebian:8123/hassio/ingress/69f7f093_frigate-proxy"
Ok iām in a similar boat but i cant get my head around a couple of things.
-
Iām stuck with being able to connect to the frigate url as per most other posts.
the urls iāve tried are : http://ccab4aaf-frigate:5000, http://<my home assistant piās Ip>:5000, http://localhost:5000. None of which work , i also cant connect to any of those addresses via my browser. -
I have enabled port forwarding on my tp link router for my home assistant pi on port 5000 for both tcp and udp
-
Iāve installed via HACS the frigate integration and obviously trying to install the frigate addon, but when faced with the popup window for the URL to enter obviously it doesnt connect so closing the window then shows that the addon has not been installed. So how does the frigate server or what ever it is get created if i cant install the addon ?
-
My TP link router is connected to my starlink router which runs CGNAT, so i can understand if this was trying to connect via the internet but iām using local addresses here so assuming the CGNAT side of things shouldnt be playing a role in this setup process and it should all be going through the TP link router.
So basically, i cant connect so i cant install the addon, if i cant install the addon then what am i connecting to ? seems like a bit of catch 22 loop if i understand it right ?
I have the same problem as ālazzaā and many others, I canāt complete the installation because I get the error message āFailed to connectā.
I have read lots of posts and tried lots of your tips, but they do not work.
I see that the files installed by HACS are where they should be, so there must be something else wrong. MQTT works and is also used for other integrations.
I am running HA on a Dell OptiPlex 7040 microcomputer, is that the problem? Is it not possible to install Frigate on such a hardware, or do I have to have a Coral TPU installed first?
I donāt want to buy a Coral TPU if Frigate canāt run on my Dell OptiPlex anyway.
Iāve tried so many times now, so I donāt understand how the rest of you have managed this.
just a FYI, for me the outcome was simple in the end, albeit a little confusing when ya reading the docs etcā¦, so you have the integration installed and now you have a error connecting to frigate as per above. Make sure you go to home assistant āaddonsā and install the frigate addon as well (and start it). I think from memory my brain said ā¦ you have the integration installed it should just work, not realising i needed the addon installed and running slaps forhead
Hi ālazzaā and thanks for the quick response.
I have done as I describe below, but is there something I have missed? Under the heading āAdd-Onsā there is no Frigate so I interpret that it has not started.
- first I install the FRIGATE integration via HACS.
- then I restart HomeAssistant.
- then I try to install the Frigate integration, but when I try to save it, I get the error message āFailed to connectā.
I have tried saving to all possible URLs but get the same error.
Is there anything beyond this I need to do? I have looked under āAdd-Onsā, but there is no Fregate, only under HACS and there I can only download Frigate again.
Edit
I forgot to mention that I have also created a frigate.yaml file
You need to learn the difference between Integration and Addon.
An integration in Home Assistant is a piece of code that enables Home Assistant to connect to a certain service. The Frigate integration in HACS is not Frigate itself. It is the software running in Home Assistant that connects to Frigate
Frigate itself must be installed - either on a separate computer - or on the same computer as Home Assistant as an Addon.
An Addon in Home Assistant is a 3rd party software which has been packaged as a Docker image and runs side by side as a Docker container.
You have to install addon. Check this out. When addon is running than you can connect to it using frigate integration.
Thanks @ddaniel
Your link meant everything and now I have finally managed to start Frigate.
What I didnāt realise was that you had to do three different installations, HACS, Add-On and finally Frigate integration.
I was so focused on the fact that the installation should be done with HACS and not with Add-On. As a non-native English speaker, I missed this as it is not clear how to proceed.
But thanks to those who have helped.
Basically it is simple. Addons are just docker containers running something like frigate. To use some integrations you need an addon or docker container running that service. Integrations in that sense is just a program that is connected to that service and is getting some data from it.
In the end of the day all integrations are just programs connected to some service that can be run locally or remotely made just to get data from that service to home assistant.
1 Like