tawny kernel
Opening port 8123 just "loads" and does not really work. SSH works but i dont know the password. Other ports like the go2rtc works.
Anyone know why it might have hung like that? All of the sudden. This is not a good thing that is happening. I cannot restart it as i dont have physical access to it.
frail lagoon
It might be a broken custom integration, card, a broken configuration or a corrupted data disk.
Without UI, physical or SSH access it is hard to tell.
tawny kernel
I have had no changes the last x days. Is there a way to extract the ssh password from backup or something?
frail lagoon
If you have an unencrypted backup, you should be able to look it up.
If it is encrypted, you would need the encryption key and a python decrypt tool.
I would expect the password to be in an options.json in the SSH add-on's tarball.
But I don't know, if plain passwords are stored or if they are hashed.
If it is a passphrase for an SSH key, it will not be extractable.
tawny kernel
Gah, it's been running for several months without no problems then suddenly today my garage did not want to open. Hehe, I bought the yellow for stability instead of my raspberry pi. Guess I have to reboot it and fix the SSH until next time. Maybe add a watchdog 🙂 Thanks for tips
tawny kernel
I got access to Dont know if there is anything secret in this or if i should upload the thing for people to maybe help?
tawny kernel
AI Summary:
Yes. One real issue stands out: a corrupt or incomplete backup file.
Error:
Can't read backup tarfile ... Automatic_backup_2025.7.2_2025-07-29_05.28_45004645.tar: "filename './backup.json' not found"
crash
→ That backup is broken and cannot be restored.
Everything else is routine:
Regular Supervisor health checks.
Normal host info refreshes.
Frequent API token updates.
Add-on warnings about deprecated codenotary fields (harmless, but should be reported to maintainers).
No crashes, panics, or disk failures visible.
If you want, I can tell you how to safely purge the bad backup and verify the rest.
frail lagoon
The more concerning thing is: "Supervisor: Disconnected".
A full reboot might fix the supervisor. Or a repair via the CLI.
scarlet tusk
If problem is not solved after reboot (not restart) then go to ha cli and type this one by one:
login
ha supervisor repair
and when operation is finished:
ha host reboot
ofcourse check internal network: dns and ntp (time)
scarlet tusk
@tawny kernel are you running the custom Entso integration??
tawny kernel
Not that I know of, a reboot fixed it, but I’m not sure what happened in the first place? Are there any places I can look for a clue?