Ok, try one more time on a fresh VM, but this time restore the backup after you complete the onboarding process (create a dummy user). Keep pinging HA in the meantime.
If that still doesn’t work, you might have to unzip your backup and grab the configuration.yaml file from there, then inspect it for anything which might cause network issues.
This is the configuration.yaml
# Loads default set of integrations. Do not remove.
default_config:
# Text to speech
tts:
- platform: google_translate
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
# Customization
zha:
enable_quirks: true
custom_quirks_path: /config/custom_zha_quirks
zha_toolkit:
influxdb:
host: a0d7b954-influxdb
port: 8086
database: homeassistant
username: homeassistant
password: HIDDEN
max_retries: 3
default_measurement: state
I can’t see anything special
Ok, try changing it to this and restore backup. It probably won’t work, but I’m basing this off the simplest possible configuration.yaml
# Loads default set of integrations. Do not remove.
default_config:
homeassistant:
frontend:
api:
# Text to speech
tts:
- platform: google_translate
automation: !include automations.yaml
script: !include scripts.yaml
scene: !include scenes.yaml
If that doesn’t work, the only idea I have left is to start from scratch and copy over unzipped files from your previous backups one at a time (except for the includes - you need those to be there) until something breaks.
I think I have found the problem. Going to explain it, because it could be useful for other people.
I saw that i could ping the VM during the boot and shutdown procedure so I investigated what could change the network behavior of the OS after startup and… found it!
It was a ZeroTier plugin misconfiguration!
I Disabled the HAOS system on the ZeroTier website and ta-dah! online again!
Thank you for the assistance! I love Home Assistant so much now 