HA failing to come up cleanly after reboot

Configuration
1

First time here. I’ve been running fine for about 6 months now with no issues.

I’m running Home Assistant 2023.2.2. My system power cycled and restarted (it has in the past with no issues) but this time I’ve seem to have lost a lot of items. I have no more HACS or Add-ons installed. I have no Add-ons to be able to access (not in any menus)

I do have a backup but it’s over a month old. If I could access the current backup on the system (which I have an automation to do nightly), I would use that but don’t know where it is from the CLI.

I’m running on direct hardware (NUC)

Any help would be appreciated.

Thank you,

My system logs have failures

2023-02-28 15:31:26.010 WARNING (Recorder) [homeassistant.components.recorder.util] The system could not validate that the sqlite3 database at //config/home-assistant_v2.db was shutdown cleanly
2023-02-28 15:31:26.585 WARNING (Recorder) [homeassistant.components.recorder.util] Ended unfinished session (id=95 from 2023-02-28 20:13:18.638155)
2023-02-28 15:31:38.522 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from supervisor (172.30.32.2). Requested URL: ‘/auth/token’. (HomeAssistantSupervisor/2023.01.1 aiohttp/3.8.3 Python/3.10)
2023-02-28 15:31:38.730 WARNING (MainThread) [homeassistant.setup] Setup of hassio is taking over 10 seconds.
2023-02-28 15:31:38.733 ERROR (MainThread) [homeassistant.components.hassio.handler] /homeassistant/options return code 403
2023-02-28 15:31:39.366 ERROR (MainThread) [homeassistant.components.hassio.handler] /supervisor/options return code 403
2023-02-28 15:31:44.256 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from supervisor (172.30.32.2). Requested URL: ‘/auth/token’. (HomeAssistantSupervisor/2023.01.1 aiohttp/3.8.3 Python/3.10)

2

These messages are kind of „normal“ after a hard shutdown.

Recommended to clear cookies and do a browser refresh.

3

Thanks, tried that and nothing. I logged out and logged back in. Same issue.

I’m completely missing the “Add Ons” menu selection also. It seems as if haos partially booted then stopped and I’m not getting everything else that was added.

Also, all of the backups that I normally have are gone (which I would use to restore if I could get to them)

4

Ok, more information that may be helpful. From the UI, I went into

Settings → Device and Services and notice that the Supervisor hassio is not loading

image

5

Seems to be related to trying to supervisor login failing. Got this message 96 times in the last 20 minutes or so

2023-02-28 15:38:33.169 WARNING (MainThread) [homeassistant.components.http.ban] Login attempt or request with invalid authentication from supervisor (172.30.32.2). Requested URL: ‘/auth/token’. (HomeAssistantSupervisor/2023.01.1 aiohttp/3.8.3 Python/3.10)

6

enable debug- in loglevel

configuration.yaml …

logger:
  default: debug

EDIT: and if possible, delete you DB-files, before rebooting your system

7

PS: if you are aware of any integrations you have “configured” in configuration.yaml , then # “commemd-out” them, same goes for automations/scripts et, if you ever made such … basically try to get your system up, with no tingle-tangle

8

Thanks. I usually edit my configuration.yaml with the “File Editor” or “Visual Studio” but these are not being loaded. Do I have access to the configuration file from the UI in another way?

Also, no Terminal access either other than direct connection to the NUC

9

Is this an IP address inside your local network?
Do you have DuckDNS/Let’s Encrypt set?

10

no samba either ? … direct access, do you mean the ha-console ? … in that case , type “help” and after each command you can type --h / --help
EDIT: connect a monitor and keyboard to your NUC, and access ha-console,

11

By the way, have you tried to restart the host after you got those issues?
If you have access to CLI, a reboot command should restart the host.

12

No this is not an IP address from within my network. I don’t use DuckDNS nor do I have access externally to HA. It’s all local

Thanks

13

Looks like an IP banned.

This should be listed on the file /config/ip_bans.yaml
If you can get access to that file, try to remove any entry to that IP (172.30.32.2).

14

No SAMBA either. I am in the NUC CLI now but the font is SO SMALL that I can hardly read it.

I noticed under “backups” that my backups do exist so I’m trying to restore them from the CLI prompt but looks like the command completes instantaneously and said it succeeded but I can’t believe that given how quickly it restored.

15

if you found ur backup folder, then /config is no far away :slight_smile:

16

they are fairly small, latest 20-30 ha backups are very very small 10-20mb, if you don’t mean some other backups ?

Thou they wont help you, if you have an IP-Ban

17

if you can run backup/restore, sounds like u have access to ha-console

try

ha su repair
AND
ha core update

18

Thanks. I did the supervisor repair but not the core update. I’ll try that one also

19

ok, then reboot, your NUC !

20

SOLVED See Link in this replay <<<<<<<<<<<<<<<<<<<<

Ok, first, thank you all for all of the help. Great group of people and very helpful.
I attempted all of the items above but nothing. I also went to the homeassistant directory and started to remove my automations.yaml files (move them out) and also some HACS integrations to see if it would help but nothing.

I then went back to the logs above with the 172.xx.xx.xx IP address and googled for this log and found the following thread.

Come to find out, this has happened to a few people with the SAME IP address. It seems that the Supervisors refresh token got corrupted and this thread describes how to repair it. I followed the steps and everything booted (or at least seems to be working now. I need to do some verification)

Thanks again for all of the help

2 Likes