My first post, so hopefully I’m doing this right. I have been running HA for a while on an Oracle VM VirtualBox with the latest releases of the OS and Supervisor. But I recently saw this message on startup on the VM. The system seems to be running and there is nothing that stands out in the logs. Wondering if anyone has any advice on what I should check out? Thanks so much. Here is a screenshot from the VM once the system starts the CLI:
Same
Thanks for the reply. At least now I know I’m not alone.
- Core ---------- 2024.2.2
- Supervisor ---------- 2024.02.0
- Operating System ---------- 12.0.rc1
- Frontend ---------- 20240207.1
You are on release candidates, which means you are on the developer versions.
You should direct your posts to the developer forums.
This is not a RC issue though, getting this on 11.5 as well
this is probably related to this: Remove shorthand for read-only mounts (#461) · home-assistant/cli@2ee0048 · GitHub
I have the same problem
1 Like
I have it too and am on 11.5. Do you know what version will include the commit you linked to? Could it be a future 12.0.rc2? I couldn’t tell by looking at github
Looking at that update it is already committed to the master branch, so it should be out soon.
2 Likes
Same issue here.
I am in OS 11.5 too.
Should I update to 12.0.rc1?
Thanks!
12.0.RC1 seems to have it too, according to this thread.
The Github link shows that the change was posted earlier today, so give it some time and an update should come.
It seems to only be related to the CLI commands.
1 Like
Thanks Wally, I guess we’ll wait for the next non-developer release of the OS and see if that resolves it. Appreciate everyone’s responses.
Seems updates are broken too
Using the terminal :
Hope we can resolve the CLI error in a simple way
A 403 http error indicates that the server have been contacted and it replied with “access forbidden”.
HA contacts GitHub, which would not normally send a 403 error, but rather a 404, so it might have contacted another server instead.
We have seen some ISPs list GitHub in their malware filters and then you get errors like that, Especially the ISP O2 have been seen doing it lately.
I’m getting the same thing here as well.
I’m also getting these error messages. Guess I’ll be waiting on en update.
When the new update is ready how to install tough
Did someone found a fix?
Not that I know of. I’m waiting on the next OS release to see if that resolves the issue. I saw the update for HA Core 2024.2.3 came out, but I’m hesitant to update anything at this point since everything works for the moment and don’t want to change anything.
I am running on laptop with OS
Happy to try the new version but don’t know how to update ha is in panic
Can someone provide a detailed, step-by-step solution for this issue? How do I fix this without having to create a new install using the latest .vdi file?
Brychance, how did you get it to work again after encountering the error. My homeassistant.local:8123 produces 404 error too.
No, I have not done anything to fix it, mainly because I have not yet seen a solution for it. The error comes up on the VM when it boots, but I can still get into HA from homeassistant.local:8123 and everything else still appears to be working. One thing strange did happen the other day when the VM VirtualBox just closed for some reason on it’s own. I’m hoping a new OS will fix the problem, but I’m backing up all my code and integrations just in case. I saw on the console a new core version came out, but I’m not changing anything at the moment.