[Errno 99] Cannot assign requested address #2595
-
Hey all, Trying to setup frigate with docker and I get this in the container logs when I restart it:
config.yml
Relevant part of the docker-compose.yml
I also know that the MQTT broker is running correctly on that port because zwavejs2mqtt is connecting to it, and so can I with MQTT explorer. I can also stream my configured RTSP streams with VLC without a problem. Any ideas? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 2 replies
-
Ah, changing my config to the local IP instead of
|
Beta Was this translation helpful? Give feedback.
-
I have exactly the same problem. But whatever I enter as the |
Beta Was this translation helpful? Give feedback.
-
It's because you are creating frigate in a container that is on a bridge network by default so any reference to localhost from inside your docker container is resolved back to the ip address of your docker container and not the ip address of the physical machine. If your MQTT broker was built as part of the same docker-compose.yaml file as frigate then, by default, they will both be placed in a bridge network called _default. You should then be able to put the docker container name name of your mqtt broker in the mqtt section of frigate's config.yaml If your MQTT broker was built in another bridge type container at a different time then you will either need to expose port 1883 from that container or recreate the container on the host network. For either of these you need to put the physical ip address or host name of the physical machine in the frigate config file and not the mqtt docker container. I guess it depends what your requirements are for your MQTT broker. If you are only creating it for the sole purpose of allowing frigate to function then I'd create an instance on the same docker network and I wouldn't bother exposing any of its ports as frigate can find it from within (assuming you configure as per second paragraph above). You may even want to include something like home assistant into the mix on the same bridge network to handle notifications. That way you have a really clean suite of applications that is containerised and (to some extent) isolated from the rest of your network and can be recreated in a flash whose sole purpose is your CCTV. However if I wanted to reuse that particular broker elsewhere on my network I'd likely build on another bridge network and expose port 1883 from that. |
Beta Was this translation helpful? Give feedback.
Ah, changing my config to the local IP instead of
localhost
did the trick 🤔