I have migrated my home assistant installation to proxmox and I get now an error message when I open the protocol in the add-ons.
Can anyone help me, I can’t find the cause.
At the moment it looks like Home Assistant is otherwise working properly.
ive got the same after i updated supervisor today
cant get any addons logs
Screen
Same here… with the issues I’m also facing with 2024.10.x regarding zwave battery operated devices, I’m now afraid to do any upgrades of anything that is core to HA.
Same Problem here.
Current workaround which is working for me:
- SSH into HA
- find docker container of addon using
docker ps - Copy container ID
- Use
docker logs <container ID>to see the logs
1 Like
It is still happening for me after 2024.11.0
Same here.
Same here.
Same here after Supervisor Update
1 Like
seems to be fixed in
Core 2024.11.0
Supervisor 2024.11.2
1 Like
Core 2024.11 is supposed to fix it and if you (like me) are still on Core 2024.10.xx, a fix is promised and in the works:
2 Likes
Sam, no workin after 11
Hello,
On my side I had the same message with Let’s encrypt and after update in 2024.11.1, it’s resolved.
Try this excellent guide. Worked for me without a problem on a Beelink mini PC. Dont forget to set bios to auto power on, esp handy after a power outage
Problem still exists on:
Core: 2024.11.1
Supervisor: 2024.11.2
Operating System: 13.2
Frontend: 20241106.2
Raspberry Pi 4
Always getting: 500 Internal Server Error for ANY Add-On in Logs
Update: fixed by down-/upgrading - now working…
Update2: Happening again for me :((
My HASS instance is updated to the latest and I still have issues. It is being a nightmare to debug any app. 
All addons display the following for some time. Sometimes it takes more than a minute before showing an error:
And this is what it is eventually displayed:
Error is not the same. It changes randomly on every reload:
Sometimes logs are displayed, but error is shown as well and logs live update is not running. After reloading, sometimes you see logs refreshed or just see another error.
Any advice, please?
I just realized that if I point my browser to the private IP, addon logs work fine. However, if I use the hostname I have for external access from the LAN, addon logs fail. I have an nginx proxy installed in my router that it is configured well. I haven’t had any single problem until now. Does anyone know if the “new” logging system listen to a specific port that I should redirect at the nginx level?
1 Like
Opposite problem for me. But seems to be related to something in the 2024.11 update. I do wish I reverted a while back but too late now.