Several days ago I had a prolonged power outage. After, I was no longer able to access HA via frontend IP address using either the internal IP, hassio.local, duckdns address, or HA phone app. I assumed a corrupt SD on Raspberry Pi 3 B+ and restored a backup successfully, but it did not restore webpage function. I am able to SSH to the device and an IP ping is successful. I can view and edit config files via Samba. Here is my HTTP config (previously working).
Ha core check shows intact config file. Attempted on multiple browsers (Firefox, Edge, etc). No success.
I checked the IP provider gateway and the public IP address is unchanged. All port forwarding is unaltered. Console command ‘ha dns info’ shows proper host dns address. Could there be a problem with host address, since it displays …32.3 vs 32.1?
When I initiate console command ‘ha core restart’, the following error appears in the log:
TypeError: _update() got an unexpected keyword argument ‘external_url’
Does anyone have any suggestions on how I can regain access to the frontend? I have no control over any devices with this issue. Please and THANK YOU!!!
can you verify if there’s a service up on port 8123?
nmap -sV -p 8123 172.30.32.3
Your nslookup seems to return a wrong ip, you could try and add it to your hosts file just for testing or temporary workaround
EDIT: you should not add protocol when using nslookup > do it without https://
To test for invalid cert you could use curl, it has a parameter to ignore invalid ssl. Curl is not in windows by default but you can find it, same goes for nmap
Thank you for the suggestions Kurt! The nmap command returned the following:
The assigned internal IP …50.222 returned a reply, but the listed dns host address does not. TCP closed??? I don’t know why the listed host address would even be 172.30…, it is not an address range assigned by my router DHCP range. Do you think this maybe the issue. When HA was working, I remember seeing occasional 172… addresses listed in my logs when there were failed login attempts internally, so assumed it was preassigned/default addresses with ha core/supervisor coding. I tried accessing HA via the 172 addresses as well without success.
DNS: your dns lookup is wrong > you should not do nslookup https://IP but only ever IP. I’m not going into that, your HA is not on an external IP
So that’s not the root cause here…
An nmap service scan on IP (-sV) returns no running services > so the service is not running… no point in searching for a cert error for a service that is not running then
A quick re-read of your problem says an error with external_url. Probably service is not starting because of that.
If you still have access through smb to your config, make a backup and make a new one, one without the cert and !secret. If no access through smb, do it through ssh, or even console. Just a simple config just to get back onto your web interface
Returns the same foreign IP address. Not my network or public IP. Not even same region. I researched with IPlookup and don’t know who’s address this is or why its there?
How did you come to this conclusion? The internal IP (192.168.50.222) that I usually connect to the UI and SSH does return a reply: 1 IP address (1 host up). Are you saying that because the TCP status is closed, that there are no services running?
I commented out all of the configuration setting in HTTP: and restarted the devices without any resolution. The problem still exist. I remember reading that there was a configuration change with the most recent updates, where the new settings would be external_url and internal_url. Is it possible that the code from the newest version was retained when I rolled back to the older 108.1 that has the backup? With that said, this same problem existed before I loaded a fresh install with newest version, hence the reason I even restored & wiped from backup.
I got the IP from the info you posted: HA DNS INFO 172.30.32.3
172.30 seems the IP from one of the docker containers…
Just for information, what is your local ip from the computer your are testing this from? For example if my local Ip is 192.168.0.x/24 The HA is on same LAN.
Just do a ping sweep on your pc (nmap -sP 192.168.0.1/24) replace with your IP to see hosts up on your network… then service scan on 8123 to see if service is up.
Sorry gonna have to leave now will check up on thread later
Would it benefit me to manually assign the internal IP address here, turn off IP ban and disable SSL? The router has been set to assign a fixed internal IP to HA. I just want local access at this point and could care less if it’s encrypted. Is there a way to remove LetsEncrypt and DuckDNS settings/addon from console? Just in case it maybe causing a conflict. Thanks!!!
Another observation, my backup .storage file has much more data that the restored from snapshot .storage file. I would think that all information would be transferred, such as lovelace, mobile_app, hacs etc, but this clearly is not the case.
Would I be better served coping all the data files from the backup .storage to the current .storage file? Are there any settings in this directory that could crash SSH and console connectivity? That is my only access at this time.
@francisp You are brilliant!!! Thank you, thank you, thank you! I removed the external/internal data from core file and was able to perform a ha core restart in console without error this time. I scoured the forum for frontend loading issues, but did not think to check for HA Docker container issues???
The UI loaded after reboot, albeit in a very unorganized/not restored layout, but at least I can access it again via local IP for further troubleshooting. I’m back on the right track thanks to your input!
Also, thanks for pointing me in the direction of the .storage file. For whatever reason, the restored snapshot did not copy all of these files and thus the reason why the UI layout was scattered. I was able to transfer the missing files manually, which saved me tons of time having to reorganize.
Once more I can’t thank you enough for the feedback!!! This is issue is solved. Cheers!
