-
Notifications
You must be signed in to change notification settings - Fork 693
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error #5797
Comments
So this comes down to having I am setting it to a private interface/ip on a vlan which has all my applications that are proxied via NGINX. Ideally I'd like to set it to be that vlan IP and 172.30.32.1 which Supervisor uses to reach Core (per what I see via So it seems my only choice is to bind to 0.0.0.0 with HAOS unless there is some other route, of a different IP for Core can be set in some way? |
I have exactly the same problem for several versions in a row. Neither automatic nor manual backup works. There is a constant process of creating a backup copy until HA reboots. It does not create a copy either on the local device or in OneDrive. Версия | core-2025.4.0 Операционная система хоста | Debian GNU/Linux 12 (bookworm) My logs:
|
I'm betting you have a similar situation. Are you setting You an see what IP and port Supervisor it trying to reach for core via In the end I had to get rid of my |
@Codelica I don't have HAOS. I have home assistant supervised. |
Yes, I saw that. But the Supervisor container still needs to communicate with Core and is failing. Are you setting |
in my configuration.yaml:
|
Interesting. Doubtful Supervisor has been banned :) I guess it still may help to see what address it's trying to reach Core on via |
Indeed, I disabled ufw on my Raspberry Pi and the backup is created without problems. Before that, there were errors in the Host log:
But I don't want to disable the firewall. I wonder what I need to add to the http section in that case?:
|
added sudo ufw allow 8123/tcp and everything works. But now I need to think about the security of this action, since I have a public IP and HA works behind a reverse proxy Nginx on RPi for remote access to HA. RPi in turn is in the local home network behind my router, on which port forwarding is configured. |
Solved the problem by adding the following rules:
|
Describe the issue you are experiencing
Ever since the "new" backup system was released I haven't been able to "complete" a backup (auto or manual). While the supervisor logs seems to show the backup is complete, and I see the backup in the lists, the spinner never stops and I can't attempt another without restarting Home Assistant. It's as though Supervisor isn't able to message Home Assistant about being done (guess). It's happening on two independent HA installations I run.
The one error I see come through in the supervisor logs that seems suspect is:
2025-04-01 10:46:55.109 ERROR (MainThread) [supervisor.homeassistant.core] No Home Assistant Core response, assuming a fatal startup error
I've tried
ha supervisor repair
and a reboot, but that didn't seem to help.What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Steps to reproduce the issue
Unfortunately I'm not sure. But seems to have started with the new backup system release. It's happening on two independent HA installations I run.
Anything in the Supervisor logs that might be useful for us?
System information
System Information
Home Assistant Community Store
Home Assistant Cloud
Home Assistant Supervisor
Dashboards
Network Configuration
Recorder
Supervisor diagnostics
config_entry-hassio-01J9YX3RFDMJHS79XEGRC06QVM.json
Additional information
All info here is from one of the two systems having the issue. It's a very simple installation compared to the other system, and I can experiment as needed on it.
The text was updated successfully, but these errors were encountered: