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.
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
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
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 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.