DuckDNS Not working:: Connection refused

Hey all, I am having issue with getting duck DNS set up. Running HassIO

I can access HA via my raspberry pi IP, but cannot hit http or https on duck dns.

I did have it working at one point but had to start from ground 0 again and now I can’t get it up. I’ve created a new domain just to test this one (The old domain seems to cache the old instance).

This is my http section

http:
  base_url: http://DOMAIN.duckdns.org:8123
  server_port: 8123
  # ssl_certificate: /ssl/fullchain.pem
  # ssl_key: /ssl/privkey.pem

commenting out ssl to get it working on http first to isolate any ssl issues

curl -v http://DOMAN.duckdns.org:8132 gives me

* Rebuilt URL to: http://DOMAIN.duckdns.org:8132/
*   Trying MY PUBLIC IP...
* TCP_NODELAY set
* Connection failed
* connect to PUBLIC port 8132 failed: Connection refused
* Failed to connect to DOMAIN.duckdns.org port 8132: Connection refused
* Closing connection 0

Any ideas on where I can more effectively debug? I’m stuck in the mud here.

Thanks!

Are the port forwarding rules in your router still there?

Are you using the same ports?

Visit the DuckDNS configuration page. Has it obtained your router’s public IP address?

@tom_l
Port forwarding rules are there. I verified the ports are open by using a website tool, same ports as before. I actually put my PI in a DMZ for the time being.
Same ports and duck DNS has my IP

Maybe you have a web browser security issue. Try clearing your cache or using private browsing mode. Add a security exception if prompted.

Yep tried that. I’ve also tried a system wide DNS clear with

sudo killall -HUP mDNSResponder; sudo killall mDNSResponderHelper; sudo dscacheutil -flushcache