Closed u20p17 closed 7 months ago
"OSError: [Errno 113] No route to host" is the mqtt server reachable from the container?
how can I test this? but I think it should be reachable because I can also reach the mqtt server from my laptop (which is in the same ip range as the container (192.168.1.x))
i am using unifi hardware, so could be a firewall issue... what firewall rules I would have to add for the mqtt communication with the docker container?
today i had some time for further debugging and I found out the following:
Test1: When I run the following docker command mqtt is working fine (bridge mode and i changed the port 80 and 443 (i know this ports must not be changed...) just for testing):
docker run
-d
--name='diyHue'
--net='bridge'
-e TZ="Europe/Berlin"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="HomeServer"
-e HOST_CONTAINERNAME="diyHue"
-e 'MAC'=' 48:21:0B:26:39:5A'
-e 'IP'='192.168.1.4'
-e 'DEBUG'='true'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:80]'
-l net.unraid.docker.icon='https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/images/diyhue.png'
-p '81:80/tcp'
-p '4431:443/tcp'
-p '1900:1900/udp'
-p '2100:2100/udp'
-v '/mnt/user/appdata/diyHue':'/opt/hue-emulator/config/':'rw' 'diyhue/core:latest'
5e811855aedc484aed28d244b8e4b9e4485b7d717a6e6d952e6d5f4a090f54bc
Test2: If I use a custom network with the original ports MQTT is not working --> same error as some weeks ago --> OSError: [Errno 113] No route to host
docker run
-d
--name='diyHue'
--net='br0'
-e TZ="Europe/Berlin"
-e HOST_OS="Unraid"
-e HOST_HOSTNAME="HomeServer"
-e HOST_CONTAINERNAME="diyHue"
-e 'TCP_PORT_80'='80'
-e 'TCP_PORT_443'='443'
-e 'UDP_PORT_1900'='1900'
-e 'UDP_PORT_2100'='2100'
-e 'MAC'=' 48:21:0B:26:39:5A'
-e 'IP'='192.168.1.4'
-e 'DEBUG'='true'
-l net.unraid.docker.managed=dockerman
-l net.unraid.docker.webui='http://[IP]:[PORT:80]'
-l net.unraid.docker.icon='https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/images/diyhue.png'
-v '/mnt/user/appdata/diyHue':'/opt/hue-emulator/config/':'rw' 'diyhue/core:latest'
882db02bdba4eca3c3456fde36024f05c1be72deb2ea9f63fcde5d5e420f5124
My mqtt settings in DIYHue were exactly the same in both tests. (mqtt server ip is 192.168.0.2:1883) Why is it not working with br0 network? :(
EDIT: I fixed now the issue! the problem was that I thought I had activated the communication between Bridge and custom network, which I hadn't... after making the change it is working!
Issue does not already exist?
I have searched and found no existing issue
Select Environment
Docker
Home Assistant related?
Yes
Description
I am trying to connect to my home assistant (192.168.1.10:8123) and/or mqtt server (192.168.1.11:1883), but both do not work... HA token is correct (renewed and copied the token several times...)
Errorlog:
Error Log for HA:
Error Log MQTT-Server:
Steps to reproduce
docker run -d --name='diyHue' --net='br0' --ip='192.168.1.9' -e TZ="Europe/Berlin" -e HOST_OS="Unraid" -e HOST_HOSTNAME="UnRaidBirgit" -e HOST_CONTAINERNAME="diyHue" -e 'TCP_PORT_80'='80' -e 'TCP_PORT_443'='443' -e 'UDP_PORT_1900'='1900' -e 'UDP_PORT_2100'='2100' -e 'MAC'='48:21:0B:55:D4:B7' -e 'IP'='192.168.1.8' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:80]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/cheesemarathon/docker-templates/master/images/diyhue.png' -v '/mnt/user/appdata/diyHue':'/opt/hue-emulator/config/':'rw' 'diyhue/core:latest' e8fcd284d49cb3279a67546c2187c3131158cf4f8fc0c62a03db10c7065b8e57
The command finished successfully!
Please enter your operating system details here
Intel NUC (NUC13ANBi7 ) with Unraid 6.12.4
What DiyHue version(branch) are you using?
master (latest)