Unifi Dream Machine xxx.duckdns.org not working

smile · November 5, 2020, 9:47pm

I have been struggling with this problem. I recently replaced my Asus RT-AC66U router with Unifi Dream Machine. I configured Home Assistant with DuckDNS and port forwarding on Asus router, had no connecting problem. Worked inside the network and outside the network.

Port forwarding configuration is same in UDM like ASUS

I can connect Homeassistant with local ip like https://192.168.1.222:8123 but can’t with xxx.duckdns.org
DuckDNS address not working anymore.

Any help would be appreciated.

cwolf22 · January 9, 2021, 3:24am

I am having the same issue after switching to UDM. Were you able to find a solution to this?

smile · January 11, 2021, 10:28am

No solution found, I have installed my old ASUS router again for cheaking where is the problem. whether it is my Homeassistant configuration or router. I was confused why my Homeassistant was not working properly. After I changed my router every thing is working fine now So That means there is something wrong with UDM settings.
Please let me know if you find anything solution.

MyKE · January 16, 2021, 4:12pm

I experience same issue as well. Bought UDM, made exactly same port forwarding.

I realized I’m able to access HA via xyz.duckdns.org:8123 from the outside (internet) but not from the lan. But what’s weird it’s inaccessible even in lan via IP (https://192.168.1.10:8123).

viper33802 · January 16, 2021, 4:35pm

Is your HA server on a separate VLAN from the machine you are trying to access it from internally?

I use the same URL to access HA internally and external and then use a Pi Hole to resolve internal requests to xxx.duckdns.org back to my HAs internal IP. In my scenario I keep my HA server in my main LAN. Here is my UDM port forword rule:

jcastro · January 16, 2021, 5:03pm

I use both at my LAN and when I’m out the duckdns domain

MyKE · January 16, 2021, 7:31pm

HA is in same VLAN as I access it internaly. No extra firewall rules applied to restrict anything, using default ones in the UDM. The only difference in my port forwarding like shown in the picture is I have allowed TCP only. Not sure if this could be the case.

viper33802 · January 16, 2021, 7:58pm

May be worth trying. I am not sure if HA needs both protocols for sure. I would have to look it up. Sorry, I do not see a picture in you post for some reason.

MyKE · January 19, 2021, 9:03am

I fixed the problem.

So the UDM was shipped with the 1.5.6 version. It did not offer any updates from update check but on official website is available 1.8.5.

I did a manual upgrade via ssh to UDM running ubnt-upgrade [FW url].

This resolved my issue. I guess there was some hairpin nat issue in the older version of the firmware.

https://community.ui.com/questions/UDM-non-pro-Hairpin-NAT/12681490-7f26-49a7-885e-2860ebdeb7e6#answer/2071928f-f436-4ebd-891c-52aac237c302