Since I use Dnsmasq I’m able to connect to my HA via the myduckdns.duckdns.org link, which is great because my router does not support nat loopback.
Unfortunately I’m facing another problem now.
First all worked great, restarting HA with no fails.
When I restart my HA now via the homeassistant_restart command, services like netatmo, tado, homekit are not able to connect.
I fix it with turning off Dnsmasq (also autostart off) and than restarting HA without dnsmasq.
In this case alls services are able to connect. After this I turn on dnsmasq manually and alls works again … till the next restart.
Also can’t acces samba share when dnsmasq is running.
What am I doing wrong?
Edit: Seems like no data will be received from netatmo (…) when dnsmasq is acrivated. It continues recording when i turn dnsmasq off.
I have the same issues when i seitch from dnsmasq to pihole.
This issues is really annoying, as I have to choose between the mentioned services or beeing able to use ha outside my local network.
I have been facing the exact same issue for a long time, using the dnsmasq plugin (my router does not have nap loop back either) for internal access…it seems to suddenly block Home Assistant from accessing any external services every few days. It’s kinda hard to troubleshoot and I could not figure out what was causing it, so in the end I bought an extra raspberry pi to run as a dedicated Pi Hole/DNS server. This seems to work so far.
So if you have an extra Pi (even a pi zero w would work) a workaround is to use an external DNS server.
I was facing the issue with different HA versions since a few months, with and without duckdns. Also, I have Netatmo as well.
I seems like I found the right section, this is where i filles in my data:
I’m not sure if this line is necessary, because I tried logging in into ha without it and it also worked. But I did not double check that.
However with this line activated (not #) it seems to work now.
I have HA installed on raspbian Pi3 and I can access from both internal or external using duckdns.org link. But when I switched to HASSIO with duckdns/letsencrypt, I can only access from external using duckdns.org link. So far from what i’ve read, the router needs loopback support. My question is then how come when HA on raspbian and letsencrypt/duckdns, I am able to access from both internal and external? Bit confused.
I installed addon dnsmasq and out of the box, it can’t start.
I have the following error on the system page :
**ERROR (SyncWorker_10) [hassio.docker] Can’t start addon_core_dnsmasq: 500 Server Error: Internal Server Error ("driver failed programming external connectivity on endpoint addon_core_dnsmasq ** Error starting userland proxy: listen tcp 0.0.0.0:53: bind: address already in use")
In my understanding, it seems that port 53 is already in use but no other container use it !
Any idea ?