[Errno 99] Cannot assign requested address

[alexturpin]

Hey all,

Trying to setup frigate with docker and I get this in the container logs when I restart it:

frigate          | 2022-01-06T06:21:58.542524232Z [s6-finish] sending all processes the KILL signal and exiting.
frigate          | 2022-01-06T06:22:45.237179095Z [s6-init] making user provided files available at /var/run/s6/etc...exited 0.
frigate          | 2022-01-06T06:22:45.270347420Z [s6-init] ensuring user provided files have correct perms...exited 0.
frigate          | 2022-01-06T06:22:45.271675519Z [fix-attrs.d] applying ownership & permissions fixes...
frigate          | 2022-01-06T06:22:45.272600914Z [fix-attrs.d] done.
frigate          | 2022-01-06T06:22:45.273605789Z [cont-init.d] executing container initialization scripts...
frigate          | 2022-01-06T06:22:45.274376136Z [cont-init.d] done.
frigate          | 2022-01-06T06:22:45.275249500Z [services.d] starting services
frigate          | 2022-01-06T06:22:45.280370462Z [services.d] done.
frigate          | 2022-01-06T06:22:45.925114944Z [2022-01-06 06:22:45] frigate.app                    INFO    : Starting Frigate (0.9.4-26ae608)
frigate          | 2022-01-06T06:22:45.945836531Z Starting migrations
frigate          | 2022-01-06T06:22:45.945884861Z [2022-01-06 06:22:45] peewee_migrate                 INFO    : Starting migrations
frigate          | 2022-01-06T06:22:45.949269013Z There is nothing to migrate
frigate          | 2022-01-06T06:22:45.949312524Z [2022-01-06 06:22:45] peewee_migrate                 INFO    : There is nothing to migrate
frigate          | 2022-01-06T06:22:45.953164682Z [Errno 99] Cannot assign requested address
frigate          | 2022-01-06T06:22:46.058453203Z [cmd] python3 exited 1
frigate          | 2022-01-06T06:22:46.063672571Z [cont-finish.d] executing container finish scripts...
frigate          | 2022-01-06T06:22:46.064433350Z [cont-finish.d] done.
frigate          | 2022-01-06T06:22:46.064889483Z [s6-finish] waiting for services.
frigate          | 2022-01-06T06:22:46.308156089Z [s6-finish] sending all processes the TERM signal.
frigate          | 2022-01-06T06:22:49.314671813Z [s6-finish] sending all processes the KILL signal and exiting.

config.yml

mqtt:
  host: localhost
  port: 1883

Relevant part of the docker-compose.yml

  frigate:
    container_name: frigate
    image: blakeblackshear/frigate:stable-amd64
    restart: unless-stopped
    shm_size: "128mb"
    volumes:
      - ${ROOT}/config/frigate/config.yml:/config/config.yml:ro
      - ${ROOT}/frigate:/media/frigate
      - type: tmpfs
        target: /tmp/cache
        tmpfs:
          size: 1000000000
    ports:
      - "5000:5000" # HTTP
      - "1935:1935" # RTMP
    environment:
      FRIGATE_RTSP_PASSWORD: ${FRIGATE_RTSP_PASSWORD}   

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!

[alexturpin]

Ah, changing my config to the local IP instead of localhost did the trick 🤔

mqtt:
  host: 10.0.0.73
  port: 1883

[snjallingur]

I have exactly the same problem. But whatever I enter as the host: (actual IP address, localhost or 127.0.0.1) it always throws this [Errno 99] Cannot assign requested address error.
I can confirm that MQTT is connecting fine from other applications. Any clues?

[ruffson]

Did you ever solve this issue? I am having the exact same problem. I am wondering if it is some firewall issue (running it on openSUSE).

[holgerschillack]

I had the same problem and had to add 1883 to the mapped ports to get it working.

   ports:
      - "5000:5000"
      - "1935:1935"
      - "1883:1883"

In the top it just says

mqtt:
  host: 192.168.178.48

[ediguidedog]

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.