josephny
June 25, 2025, 4:21pm
1
I’ve had an HA instance running in Proxmox for years.
Over the past several days I fought a fierce battle to upgrade core from 2024.10.4 to current and finally (with a lot of help from the people here) succeeded.
It worked until a restart, and now I have no UI access (that is: access locally via a browser pointing to 192.168.0.103:8123). I’ve tried different browsers, as well as the HA app on my cell phone.
I can access the CLI via console in proxmox, as shown below.
And I restarted the VM in proxmox and watched it load – did not see any errors or failures.
I can ping 192.168.0.103 but running a port scan does not show 8123 open.
Ugh! Please help.
francisp
June 25, 2025, 4:24pm
2
Start with the usual troubleshooting, on that page, enter
ha supervisor repair
ha core rebuild
josephny
June 25, 2025, 4:34pm
3
Both commands issued.
“supervisor repair” took about 5 minutes and respond with ‘success’
core rebuild responded with:
“unknown error, see supervisor”
Still no http access or open port 8123
josephny
June 25, 2025, 4:35pm
4
Also issued:
ha core restart --safe-mode
and got the same error (“unknown error, see supervisor”)
josephny
June 25, 2025, 4:40pm
6
I don’t know how to get to that log without UI access.
francisp
June 25, 2025, 4:41pm
7
On your proxmox console, just enter
ha supervisor logs
josephny
June 25, 2025, 4:47pm
9
Seems plenty of other services are working:
josephny
June 25, 2025, 4:48pm
10
shooting in the dark here and thought to enter this:
francisp
June 25, 2025, 4:51pm
11
Last lines of your log screenshot shows
So either Supervisor is downloading the docker, or it failed to download the docker
josephny
June 25, 2025, 4:54pm
12
What can I do or check next?
I rebooted the VM again, and ran “supervisor logs” and got the following:
josephny
June 25, 2025, 4:57pm
13
I check port 4357 and it says all is well:
francisp
June 25, 2025, 5:02pm
14
Seems adguard is the problem
ha dns options --servers dns://1.1.1.1
ha dns restart
or
ha addons uninstall a0d7b954_adguard
josephny
June 25, 2025, 5:09pm
15
I uninstalled it, rebooted the VM, and same problem.
I think adguard has been a problem long before the current failure, so it’s not surprising.
francisp
June 25, 2025, 5:10pm
16
did you try the dns settings ?
josephny
June 25, 2025, 5:11pm
17
Do you mean the adguard settings? I thought uninstalling it would be cleaner.
Current supervisor logs:
francisp
June 25, 2025, 5:12pm
18
these
ha dns options --servers dns://1.1.1.1
ha dns restart
josephny
June 25, 2025, 5:14pm
19
done.
No change.
Why wouldn’t 8123 be open?
francisp
June 25, 2025, 5:15pm
20
home assistant container is not running
