#HA Blue - Supervisor no host internet
ivory burrow
More advice/help needed. I reflashed the Blue following https://www.home-assistant.io/common-tasks/os#flashing-an-odroid-n2 which worked ok, apart from I got message saying PetitbootFaile, dropping to a shell. I proceeded given I wanted to Exit to Shell anyway. The prompted kept indenting each line, but otherwise reflash completed fine (haos_odroid-n2-7.6.img.xz) . Switched boot back from SPI to MMC and restarted with everything connected. I get the HA splash screen saying it is being prepared, but it just hangs on that screen. Clicking on the blue circle to view the log, has a similar error message to original - supervisor has no host internet connection.
Would really appreciate help to talk me through what I can try next. I've gone from a working HA Blue that couldn't update to now not being able to access at all so am in a pickle.
I've started this as a thread to keep of the main discussion - but please advise if I am asking for hep in the wrong way
dry ginkgo
Do you have any Special network configuration in your home network (Firewalls, managed switches, proxys etc)?
ivory burrow
No, I don't think so. Have a Deco Mesh wireless network with one of the hubs cabled to a network switch that in turn has a cable to the HA Blue. Firewall via the Deco (& poss my cable router) but nothing on top of that. That set up has been in place for at least a year and I think predates the blue. The Blue has a static IP address reserved on the Deco which again has been in place since the start. I also have HA configured in Cloud via NabuCasa (not currently connected)
HA was receiving feeds from phone locations and updating family locations, and also connecting to a Eufy camera feed, when I haven't been able to update Supervisor, so as far as I'm aware was connected to internet. I was able to ping google.com when looking at the Network Info via terminal previouly
I've moved it for now to a different location and wired directly into a different Deco node. Not sure if that was the difference but this did take me straight into a new install which has almost current versions of OS/Core/Supervisor although there is 1 update pending for supervisor. However, I've loaded a backup but it won't let me install.
22-04-27 14:03:01 INFO (MainThread) [supervisor.jobs] 'BackupManager.do_restore_full' blocked from execution, system is not healthy
I've also tried to update Supervisor but got following errors
Login attempt or request with invalid authentication from 192.168.68.101 (192.168.68.101). (Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/100.0.4896.127 Safari/537.36)
14:42:44 – (WARNING) HTTP - message first occurred at 14:42:44 and shows up 2 times
[281473570039600] Error updating Home Assistant Supervisor: Abort update because of an issue with AppArmor: Can't fetch AppArmor profile https://version.home-assistant.io/apparmor.txt: Cannot connect to host version.home-assistant.io:443 ssl:default [[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1129)]
14:32:11 – (ERROR) Home Assistant WebSocket API
ivory burrow
Small step forward to connect to another instance, but it looks like whatever the issue was wasn't fixed by reflashing. Going back to your original comment, does this suggest the issue is with the instance configuration as the problem still exists and is stopping me restoring
dry ginkgo
Yeah definitly a network or a supervisor issue.
You said it has a stativ ip adress. Is there maybe a ip conflict you didnt see? Or is your HA instance available from the internet and Something else is running from.port 443 or ssl certificate issue?
According to the logs at the end there seems to be any kind of ssl issue (your connection error relies on a ssl issue). Also theres a authentication issue wirh ip adress 192.168.68.101. as long as this is a ip adress of one of your client devices from which you access your instance, you could try to log out, clear.browser cache and log in again
AppArmor is as far as i know a protection mechanism from supervisor which protects your instance.from.security risks from addons (which the supervisor itself also is).
In both cases my expertise is reached by now, but network and supervisor people seem to be the place.to ask for more detailed help
ivory burrow
Thanks so much for your help. I'll double check ip addresses but don't think there is any confict. Not sure how to check ports/certificates but I'll look into it. the 101 ip is for my laptop that I'm trying to access HA on so that could be an issue. Will clear that out first and see if that makes a difference
dry ginkgo
The part with the port is easy: obly webserver which are reachable from the internet run on 443. So the question is if you have setup anything web related at your network which is reachable via the internet via a url