Hi All,
My internet goes down quite often. I thought that using DuckDns or local IP would work but it doesn’t.
I tried my DUCKDNS link, nothing.
I tried hassio.local:8123 and my Raspberrypi IP:8123 I get the login screen but as soon as I login I get the error: Unable to connect to Home Assistant. retry. Hitting the retry does not help. Screenshots attached.
Port-forwarding screen grab also attached.
I read several pages online but cannot figure it out.
Please help.
Using Hassio on Raspberry Pi 3 B+
HA app error also attached.
Here is a Update and I still need help.
With the internet ON I can access https://myhome.dusckdns.org and http://192.168.1.xx:8123. Note- no HTTPS with IP address.
However when the internet is down - I cannot access any of the above.
If I leave the https://myhome.dusckdns.org open on my browser - things work, until I refresh the page. All buttons and sensors still work with Homekit.
Only FRONTEND is DOWN.
my setup now is - Hassio, DuckDNS, DNSMasq. I use the Orbi (No NAT loopback).
I tried the NGIXN proxy manager and HA SSL proxy - neither worked - INTERNAL ERROR when trying to generate the SSL certificate.
Any help please…
If you can’t access it via IP address your network is fundamentally broken. The local IP address doesn’t rely on the internet to be up.
If you have your http:
section configured to use certificates and you can access your instance without https, then your home assistant is broken. It shouldn’t allow any traffic to http if you have told it to use https
I don’t know. Https does not work on IP on or without internet. I think it’s a HASSIO issue.
This is my 3rd install of HASSIO and all 3 have the same problem.
The only things that work with the internet working as mentioned earlier are https://mydomain.duckdns.org and
http://192.168.1.xx
Without internet locally
https://mydomain.duckdns.org/ - does not work
http://192.168.1.xx works on PC (host file edited)
App does NOT work, Chrome/Safari does NOT work on Phone either.
The error- Unable to connect - Retry (the login page appears, but after login /pwd, error appears)
Stop editing your private IP out. We can’t get to your 192.168.
What does host file edited mean?
On my tablet it does not work either. I have to use https://home.mydomain.com. On my Windows PC it works, after I accepted the ‘wrong’ certificate.
Host file in windows. You can select ips to allow or block.
I know how hosts files work in OSes…I was asking what you meant by that statement. You didn’t clarify anything.
Doesn’t say anything.
I had an issue today where my HA (rPi 4B) stopped working properly. A few plugins (tuya and honeywell) did not find the devices, a restart of HA did not fix it. After a bit HA would not boot.
I reinstalled HA fresh, and restored a working backup.
Ever since then, on my laptop that I was previously using I cannot login using Chrome. I get the “Unable to connect to Home Assistant, RETRY”
Using the same laptop, IE works to login.
iOS app works to login.
My windows 10 Tablet works to login using Chrome.
I have cleared EVERYTHING (clear browsing data, Advanced, All Time, select ALL, Clear Data) and I still get the same thing.
Any ideas? As I said, this was working before, but now it is not. No settings changed on my laptop.
Hey,
Did anyone manage to fix this issue?
I am facing the same issue, I am able to login from outside the network on the iOS app but i cannot using the android app or a web browser. Gives me the same error as what is shown in the beginning of the thread.
Any help would be much appreciated. Thanks in advance.
Regards
Hi,
Same issue here too. Can access ha on chrome on mac via local ip but app doesnt work mobile browsers dont work.
Anyone out there got a fix? Will be much appreciated.
I still have the issue, so I did not find a fix. Seems like Hassio needs to have internet to work. But for some reason on the PC it doesn’t.
I’ve been searching a long time for an answer.
I have this same issue.
From home I can login with the local IP, or, …with the duckdns url on a Incognito browser window (can’t understand why). It does not work on a “normal” browser window, only incognito.
Hi Flink,
I’m glad you brought this up again. I finally figured out a way to solve this issue.
So once you’re done with duckdns and it is working you need to do a couple of things.
Install DNSMasq and add DNS on your phone (to make it work on the iphone).
dnsmasq config -
defaults:
- 1.1.1.1
- 8.8.8.8
forwards: []
hosts:
- host: your.duckdns.org
ip: 192.168.1.xx #this is your internal IP address - mine is my rasp pi
This should fix the computer/chrome issue.
To make things work on your iphone even without internet (locally)
Go to wifi>select (i) next to the wifi network>select configure DNS - manual>Add server - here enter your internal IP (same as above).
One last step if you’re usnig the HA app on the phone, Connections> Internal URL - add your.duckdns.org. the phone will automatically switch to Internal URL when you’re home (which is much faster).
Hope this helps.
Hi,
I am getting this from time to time in my PC browser. It works the whole time and from one to another I get this error and most of the time only a restart of the browser fixes the problem. During that problem I still can access HA with my cell phone.
Any advice please
Thanks!
Hello. I had the same issue. In y case I solved:
private navigator and it works. So, the problem I think it’s the cache.
Thank you!
Hi, i have similar issue, but in my case only on one device (PC win10), and just after switch from duckdns to cloudflar tunel. All the rest devices working realy nice , insted this one - not posible to load HA, and only using cloudflare tunel (local connection working normalny).
What can be the issue of that case?
Cache cleaning not works (also private mod of browser), chrome and EDGE also…
None of the above solutions worked for me so I thought I’d add what solved it for me. I had no errors in home-assistant.log, no ip_ban, no browser cache issue, did not work after restart HA, etc.
My case was that my letsencrypt certificate expired today and the automation in cron (https://dehydrated.io) didn’t seem to have renewed it in time. Oddly running dehydrated manually worked and HA resumed working. So to avoid this head scratching the next time the cert expires, I need to figure out why the cron job didn’t work.
It would be nice if HA gave a more helpful error in this situation.