HA running but I can’t access from any of my devices. How can I fix from the CLI?

Installation
1

Hello, I’m assuming a recent update has somehow broken remote access. I have my HA configured for remote access using DuckDNS and Let’s Encrypt. I recently lost the ability to connect to my HA from any of my devices (iPad/iPhone App, Web browser). The only access I have is from the CLI directly connected to the Raspberry Pi 4. Other posts with a similar issue seem to at least have some connectivity.

I then tried to restore from a backup from more than a month ago with a fresh install on another SD card but after waiting more than 12 hours for the restore to complete, I did a reboot but still no access to the Web UI. I’m now realizing that I should have tested the recovery process.

So I’m back to seeing if I can get access to my HA from any of my devices. The error I get from my iPad app is

Invalid HTTP response (403) for https://xxxxxxxx.duckdns.org/auth/authorize?response_type=code&client_id=https://home-assistant.io/iOS&redirect_uri=homeassistant://auth-callback.

Domain:

HomeAssistant.OnboardingAuthError

Code:

1”

Given I only have access using the CLI any pointers on where to go from here would be greatly appreciated.

2

Connect a screen to your Pi. See what address it uses. Use a browser to go to http://address:8123 . Ignore the warning about invalid certificate.

3

Thanks Francis, I’ve already tried that. I get

“Safari can’t open the page because the connection was lost.”

4

It would be nice to ignore the certificate and login as Francis suggested so I thought I could do something from the CLI. So I log’d in from the ha prompt

login

Couldn’t find any reference to where the configuration.yaml in an online search is so did a

find -name configuration.yaml -print

which gave the location and then I used vi to comment our everything in the http: section related to SSL

resulting in

‘http:’
‘# ssl_certificate: /ssl/fullchain.pem’
‘# ssl_key: /ssl/privkey.pem’
‘# ip_ban_enabled: true’
‘# login_attempts_threshold: 5’

then did a

exit

and rebooted the HA.

I was then able to use the URL suggested by Francis and get in without a warning about invalid certificate.

At least now I am able to access my HA via a browser or app locally on my network. Now I just need to figure out what is broken with the remote and secure access using cerfificates and also look at what’s going on with the backups.

Hope this is useful.

1 Like
5

I guess I’ve faced the same issue, I got the latest core update and SO update, did both and after that I couldn’t access HA from anywhere, just from CLI from the virtual machine. In my case was that the interface “eth0” was suddenly disabled, you can check it with the command network info and look within the interfaces section for the eth0, it should say “enabled: true”, but in my case it was false, so I ran the following commands from CLI to enable it:
network update eth0 --ipv4-method auto
And then
network reload

Then just hit F5 on the browser and it was back online, I hope it is helpful to you too.

6

I finally figured out the problem. Not sure how it happened but somehow my IP address had been added to the IP banned list. Once I removed it from the list, I was able to remotely connect without issues.