Skip to content
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

[BUG] New chrome update breaks dashy #1820

Open
5 tasks done
wioch opened this issue Feb 21, 2025 · 0 comments
Open
5 tasks done

[BUG] New chrome update breaks dashy #1820

wioch opened this issue Feb 21, 2025 · 0 comments
Assignees
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working

Comments

@wioch
Copy link

wioch commented Feb 21, 2025

Environment

Self-Hosted (Docker)

System

Chrome 133.0.6943.127; OS: Fedora 41

Version

3.1.1

Describe the problem

New chrome update (to 133.0.6943.127) breaks Dashy 3.1.1 and this error is presented:
`It looks like something's gone wrong...

This is likely caused by the app source not being found at the current domain

If you need additional support, check the browser console then raise a ticket`

Dashy is working correctly on other browsers like Egde, FF or Opera.
No relevant logs from docker logs command.

Chrome console shows this when trying to load dashy:
net::ERR_CONTENT_LENGTH_MISMATCH 200 (OK)

And screenshot of errors:

Image

Same on Chrome topic here:
https://www.reddit.com/r/chrome/comments/1itzn7d/err_content_length_mismatch_chrome_v133x/

Additional info

No response

Please tick the boxes

@wioch wioch added the 🐛 Bug [ISSUE] Ticket describing something that isn't working label Feb 21, 2025
@github-project-automation github-project-automation bot moved this to Awaiting Triage in Dashy V3 Feb 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐛 Bug [ISSUE] Ticket describing something that isn't working
Projects
Status: Awaiting Triage
Development

No branches or pull requests

2 participants