-
-
Notifications
You must be signed in to change notification settings - Fork 32.5k
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
aiohttp.server error in 2024.10.0b2 - Host 'homeassistant.local:8123' cannot contain ':' (at position 19) #126961
Milestone
Comments
Its fixed in 3.10.7. I've been trying to release it for the last few hours but docker registry has been down |
bdraco
added a commit
that referenced
this issue
Sep 27, 2024
changelog: aio-libs/aiohttp@v3.10.6...v3.10.7 fixes #126961
https://www.dockerstatus.com/ still shows an active incident but it seems to be releasing now on attempt 3. Sadly each attempt takes about 70 minutes |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The problem
The yarl bump in #126872 has seemingly caused broken functionality in the Frigate Card, it's no longer loading any thumbnails for events/clips gallery or snapshots gallery after updating to 2024.10.0b2 and is printing hundreds of errors in the logs. (Have since upgraded to b3 as well, same issue).
I can create an issue on their repo if it's something that should be addressed on their end. But it was working fine in b1 and broke in b2.
EDIT: It's not just the Frigate card, but Frigate snapshots in general. Push notifications to phone have broken image attachments too (500 forbidden error).
edit 2: left home and it works fine when on my external Nabu Casa URL, it's just the internal URL (homeassistant.local:8123) with issues.
What version of Home Assistant Core has the issue?
2024.10.0b2
What was the last working version of Home Assistant Core?
2024.10.0b1
What type of installation are you running?
Home Assistant OS
Integration causing the issue
No response
Link to integration documentation on our website
No response
Diagnostics information
No response
Example YAML snippet
No response
Anything in the logs that might be useful for us?
No response
Additional information
I have IPv6 disabled in network config if that matters
The text was updated successfully, but these errors were encountered: