Correct me if I’m wrong, but I should still be able to use https://hassio.local:8123 to access the front end on my local network, right (without DNSmasq)? That is the part that seems to be broken. As of right now, if I try that I get the following log:
2018-05-23 07:44:00 WARNING (MainThread) [homeassistant.setup] Setup of config is taking over 10 seconds.
2018-05-23 07:44:11 ERROR (SyncWorker_2) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-23 07:44:11 ERROR (SyncWorker_2) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-23 07:44:11 ERROR (SyncWorker_2) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
2018-05-23 07:44:11 ERROR (SyncWorker_2) [homeassistant.core] Error doing job: Task was destroyed but it is pending!
I did a quick test this morning and adjusted the base_url, and I was able to login from an external network (when specifying port 8123), which is awesome! I will try the DNSmasq add-on tonight, and an additional port forwarding rule so I don’t have to specify the port at the end.
That’s normal. I have to add a security exception to my browser to use that address as the SSL certificate is not for the local url but for the duckdns url. Sounds like you got it working.
I can get https://hassio.local:8123 locally using Chrome on my WIndows PC but it complains about not being safe. Like tom_i says, to use https you must go through duckdns. This makes DNSmasq necessary even for local access. I would keep using port 8123. (443 is the default if you really want to try eliminating the port number)
Unfortunately, the ERROR in your log file is the new normal. It showed up in HA 0.66 and affects everyone using https.
Hey guys, I think I pretty much have everything wrapped up. I’ll post my final procedure in hopes that it helps at least one person with their setup! Thanks to everyone for all of
the assistance, especially @tom_l!
Restore modem to default
Restore Pi3 SD to hio 0.69.1
Verify hassio.local:8123 works
Snapshot
Assign Pi3 static IP address in router/reboot router
Install SSH server
Setup and verify SSH connection with laptop
Snapshot
Setup basic “homeassistant” info and http pw in configuration.yaml
Enable port forwarding of 8123:8123 to Pi3, restart router
Verify internet works, SSH works, hassio.local:8123 works
Navigate to http://...:8123 with the IP address found in previous step
If you can’t access via your home network, loopback may not be supported. Try from
a completely external network, such as your cellphone without WiFi on.
Use hassio.local:8123 on local network if loopback is not supported
Make sure to attempt to login with your http password set previously
http:
# Secrets are defined in the file secrets.yaml
api_password: !secret http_password
# Uncomment this if you are using SSL/TLS, running in Docker container, etc.
base_url: mydomain.duckdns.org:8123
ssl_certificate: /ssl/fullchain.pem
ssl_key: /ssl/privkey.pem
ip_ban_enabled: True
login_attempts_threshold: 5
If you want to remove the port specification from external sites, you can change your port forwarding rules from 8123:8123 to 443:8123 - then reboot your router. For some reason this would not work for me, but I think it has more to do with the port forwarding configuration in my router. Access is then via https://mydomain.duckdns.org
At this point trying to go to https://hassio.local:8123 does not work (loads login page but never connects after a password is put in), but using my static IP does (eg https://192.168.0.254:8123) - even after accepting the invalid SSL certificate for the local host. I’m not really concerned about it because I will be setting up DNSMasq anyway. Thanks again!
Great work, could you please help me out with the same i worked with all the possible troubleshooting. But still, I am unable to get my hass on the duck DNS.
note:
i believe my network is cgnat, the wan ip is currently PPPoE configured and the public ip is different from wan.
tried port forwarding 8123>8123 and from other network as well
also followed other steps by uninstalling and reinstalling duck dns plugin by enabling port forwarding 443>443, 80>80 and after staring the service deleted 80>80 and configured for 443>8123
No luck, am i missing something ??
All the codes on the config.yaml looks good, i am 100% sure its on the network side
I was having the same issue tonight and after 2 hours of banging my head against my PI I was able to get it working. @zeus’s post on may 23rd didn’t quite work, but got me closer than anything else… so follow that VERY CLOSELY!!
I finally decided to throw a hail mary and began forwarding ports from suggestions I found in several different posts around the community.home-assistant.
I have 8123 > 8123, 443>8123, and 80>8123
I am going to start slowing removing them to see which one is working for me… but hopefully, this helps someone else!
Thinking back it is also important to type in https://XXXX.duckdns.org in your browser rather than just XXXX.duckdns.org - that may have been my problem the entire time as I cant remember if I explicitly did that after following zeus’s instructions. I just realized that was the problem after having issues with my phone. Something to do with cookies I’m sure.
I contacted my ISP and placed a request to open the ports. It works now, Issue resolved and it was done for free yeay . Thank you all for your support…
But still i dont think this as a better solution, hoping we get a better alternative.
The Duckdns Add-On doesn’t seem to support IPv6 yet.
Since i didn’t have an actual IPv4 set up for my connection anymore, any requests for IPv4 adresses would be tunneled to my IPv6 to which the Duckdns Add-On cannot connect.
My ISP was able to set-up an additional actual IPv4 for my connection. Now everything works like a charme.
That’s good to know… Duckdns itself supports IPv6 just fine though and if you have a static IPv6 prefix from your isp you could update the IPv6 address manually once as then it won’t change.
I’m not using the duckdns addon as I have a script to update it - but my address is static anyway…
Secure Connection Failed
An error occurred during a connection to 192.168.0.232:8123. SSL received a record that exceeded the maximum permissible length. Error code: SSL_ERROR_RX_RECORD_TOO_LONG
The page you are trying to view cannot be shown because the authenticity of the received data could not be verified.
Please contact the web site owners to inform them of this problem.
Update:
I can still access the GUI using 192.168.0.232:8123, which according to the documentation this should not be possible.
OK…this is about the 273rd discussion/tutorial I’ve read/watched for duck DNS. I’m having the EXACT same problem. I can only connect locally now using https which means something is working right. I can ping my url xxxx.duckdns.org and I get a response. Again, something is working. But I CANNOT connect to the url. Chrome says, “The site can’t be reached. The connection was reset.” Safari says, “…cannot open the page because Safari cannot establish a secure connection to the server xxx.duckdns.org.” I’ve tried connecting on my phone with WIFI off. I have port 443 forwarded to 8123, 8123 forwarded to 8123. I am not on CGNAT. What can I do?! I would just chuck the whole thing but I need a URL to make SmartThings work. Anyone??
I have two home assistant systems. Both on a Rasberry pi.
One is on my home network. There, DUCK DNS works well.
The other system I want to connect to a TP link modem with 3G / 4G sim card in. This system I do not get to work. What do I need to do differently when it connects to a 4G modem?
. Thank you all for your support…