Duckdns not working with : ERR_CONNECTION_REFUSED

Folks,
I do have a Portfreigabe in my Fritzbox for 8123
I do have a script updating my Duckdns IP as described on the Duckdns.org page.
When I use this duckdns name I still get a ERR_CONNECTION_REFUSED

Can anybody help where that comes from. A ping on that name resolves the IP very well.

are you adding :8123 to the end of your “subdomain.duckdns.org” address?

What/where are you trying to access from? A lot of enterprise setups (my work for example) block traffic on a lot of ports, 8123 included.

http://subdomain.duckdns.org:8123 and http://subdomain.duckdns.org:8123/ is what I am coping into my Safari Browser here on my mac sitting at home without and VPN
Ping subdomain.duckdns.org does resolve the address to the same I do see on my duckdns.org page.
I run a Fritzbox 6490 cable.
I run a AIO homeassistant on my Raspberry PI

What happens if you type your IP:8123 into your browser?

Since you are using http:// I am assuming your not using any encryption?

IP is working fine and great. No https only password
My Fritzbox shows this:
Datum Protokoll Port an Computer an Port
08.11.2017 19:06 TCP 8123 home-assistant (192.168.1.80) 8123

And just to be clear you are using your specific duckdns subdomain not actuallly subdomain.duckdns.org

sure, my subdomain was and I changed it so that#s why I can use it houseautomation.duckdns.org.
I do see houseautomation in my duckdns.org screen after logging in, the IPs are are in sync, the PI cron scrip is running.
The ducksh.log is ok. Time of the logfile was 2 minutes ago, so the cron is alos working with the duck.sh script

http://houseautomation.duckdns.org:8123

or

http://95.13.2.123:8123

…the ip address which came back when I did a nslookup houseautomation.duckdns.org came back with the same result.

Diese Website ist nicht erreichbar

.duckdns.org hat die Verbindung abgelehnt.
Auf Google nach duckdns org 8123 states suchen
ERR_CONNECTION_REFUSED

Could it be that you have a DS-Lite connection? With those external access is not so simple to set up.

I’m having a similar problem, I can connect via my IP, but when I go though duckdns.org, I see the logo, but when I enter my password and click connect, I get ERR_CONNECTION_REFUSED.
Were you able to figure it out @Juergen?

I do have DS-Lite as @danielperna84 mentioned. Fritz is working on a solution. AS long as they don’t have one I can tunnel

I should clarify. I can access the system with the internal IP, but external IP or DUCKDNS doesn’t work. I called the ISP and they claim to not block any ports. I also am able to log into MQTT via the DuckDNS address (meaning that part is mapped correctly). So I feel like Home Assistant is not liking me accessing it from a secure IP (maybe?). I don’t have any trusted_networks setup in my config.

1 Like