Then there is something else wrong with your setup. Not having a NAT loopback capable router will only stop you resolving the duckdns address inside your network.
Another problem (that I just personally encountered) is that some internet service providers block incoming port 443. Check with your provider if you are still having trouble.
1 Like
I started from the beginning, having issues again, so thank you, will check that
Yes I switched ISP a few months back and HA stopped working. They block a bunch of ports by default but unblocked on request and everything is good again. Definitely worth checking.
I finally found port blocks in firewall, now there is no blocks, but everything is the same. I can access to HA with https://192.168…(chrome is angry saying that it’s unsafe) but of course only from local network. Refuse to access from …duckdns.org from local network and out of it…
Did you check with your ISP if they are blocking incoming port 443?
I called to them (actually 3 times) and they all said that they didn’t block any ports. All blocking is controlled by me in router config. Don’t know another way to check that. So, again, it was blocked in firewall, i just allowed all ports
I’m out of ideas then, sorry.
Thank you for help.
Will keep trying.
I got working this stuff
In router settings set up DHTP, not L2TP
Still does not work from local network (because of nat loop), but it is fine from LTE connection.
2 Likes
Hey there! From last comment I have closed all ports again for being safe (as I know now it was not safe)
So now I am again in trouble with remote access. I called to provider’s support, they said, that ports maybe would open automatically by port forwarding if I will update my router. So I have updated my router and now magic has happened: I was able to access to HA via my_domain.duckdns (port mapping 443 - 8123 by TCP protocol as was before). But I can do that only when I am home. If I turn of wi-fi - I will not be able to reach HA. Maybe you can give some advice?