-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
Loading of website details fails (on Edge Desktop) #2832
Comments
same |
Try disabling your adblock. |
Disabling AdBlock solved the problem. thanks for the help! Maybe this information should be placed more prominently in the docs (at least i did not stumble over this information)? |
Same here. I'm not sure which of the mentioned requests triggers the error in the UI. But it would be very nice, if the site would not crash, even if these requests are blocked. In my understanding, none of these requests are necessary for Umami to work properly, right?! It would be wonderful, if we could keep using Umami WITHOUT disabling Adblockers. |
Firefox with uBlock Origin enabled has the same problem, umami is not even visible after clicking the details link as the website completely fills with next errors. Disabling uBlock Origin makes it work again. |
Describe the Bug
I have installed umami using docker-compose on my server.
i have changed nothing in the configuration exept of the server port.
Server is up and running and counting visits. But today (after running for <24h) i can't open the website details on desktop Edge anymore (see below) - while opening the details on mobile or Desktop FireFox is no problem.
Steps:
The UI shows the following error:
Clicking "OK" seems to reload the page and the error reappears.
The Browser console shows some errors:
If i select a different time frame before clicking "View details" the error does not show and everything works. Error only seems to occure when time frame is set to "Last 24 hours" Maybe a bug in the calculation since my instance has not been running for 24 yet?
Database
PostgreSQL
Relevant log output
Which Umami version are you using? (if relevant)
2.12.1
Which browser are you using? (if relevant)
Edge 126.0.2592.87
How are you deploying your application? (if relevant)
Docker
The text was updated successfully, but these errors were encountered: