Duck dns problem again (after new modem)

Well i did get a new modem from the isp, i can access XXXX.duckdns.org from my mobile phone on 4g/5g with no problem, but i can’t use it local.

port forwards are still the same:
443 > 8123
8123 >8123

i have a ddwrt router and did not change any settings, i just change modem from isp…

what could be the problem?
on https://192.168.XXX.XX it works normal,
but not with https://XXX.duckdns.org from local
https://XXX.duckdns.org from iphone on 4g it works normal.

getting ERR_CONNECTION_REFUSED


image

Try porting 8843 on the internet side to 443 on the pi.
and 8388 on the internet to 8123 on your LAN

But you need to set up nginx first.

Some residential ISPs block 443

Try

https://XXX.duckdns.org:8123

ngix doesnt even work that great, i did try that but no luck.

i just got a new modem by the same isp.

when i use my iphone that is not connected on my lan i can access the duck dns normally
port 443 is also open i tested it with the port scanner

i did try that aswell, no luck.
cant connect to duckdns from lan

Google for Local loopback (Hairpin NAT) on DD-WRT.

i did see that topics about the loopback, but thats with the old firmware, my firmware recently upgraded, and it was working…

the only thing it changed was my new isp modem, no changes in ddwrt.

So now is the question, does it something have to do with iv6 ? because this new modem is using ipv6 and ipv4 now.

so i did this:

8123 > 8123 both because tcp doesnt work = open
443 > 8123 tcp = open

so when i open port 80 > homeassistant ip, it doesnt open
when i open port 80 > nas its open but getting connection refused…

so it must be an other problem then?

i did follow this tutorial,
https://olbrecht.net/2019/12/13/home-assistant-remote-access-networking/

still giving me a connection refused… while addguard is working, so when opening a port to my nas i get the same issue, connection refused… my ddwrt router did not change or the settings…

UPDATE!

For now i got it working with addguard, using https://XXXX.duckdns.org:8123 but when adding this line in the app it does say it can’t connect, but when i go on a browser from wan it opens normally, only i can’t use the app anymore…

any idea’s ?

hours and hours tested and i got it working with addguard. On my android phone it works aswell.

so what i did is rewriting the dns in addguard and using the the ip of the machine addguard is on as dns and it worked, so i added it as default dns in my ddwrt router. on ios u need to reinstall the whole app to function, and on android it works when changing the url to https://xxx.duckdns.org:8123