Errors with Chrome Browser

Hi there,

we currently run Sentry On Premis 20.10.1 on Ubuntu 20.04.
Since a few weeks we encounter strange errors. User can’t access Sentry Web Interface via Chome Browser anymore.

Chrome Browser shows “Please wait while we load an obnoxious amount of JavaScript.
You may need to disable adblocking extensions to load Sentry.”

Browser Console Log:

(index):39 GET https://sentry.example.de/_static/1620553918/sentry/dist/vendor.js net::ERR_HTTP2_SERVER_REFUSED_STREAM
(index):46 GET https://sentry.example.de/_static/1620553918/sentry/js/ads.js net::ERR_ABORTED 404
(index):46 GET https://sentry.example.de/_static/1620553918/sentry/js/ads.js net::ERR_ABORTED 404
(index):81 Uncaught ReferenceError: $ is not defined
    at (index):81
(anonymous) @ (index):81

We are running nginx as reverse proxy.
Firefox is no problem.

We see several CanceldErrors in the internal project. See this paste: { "event_id": "9fad71c3464d4b65bee22faa3c650bba", "project": 1, "releas - Pastebin.com

Does anyone has some hints for us to solve this problem?

Thanks!

Pretty sure you are using a paranoid AdBlocker that now blocks our main JS bundle. See ingest.sentry.io · Issue #6963 · easylist/easylist · GitHub

Thanks for your reply. I’m sure I use Chrome in default settings. There is no ad blocker I have installed. Just Chrome without any extensions.

And all our users have the same problems, too. Well, some console error appears in Firefox too:

GET https://sentry.example.de/_static/1620640325/sentry/js/ads.js [HTTP/2 404 Not Found 304ms]
The resource from “https://sentry.example.de/_static/1620640325/sentry/js/ads.js” was blocked due to MIME type (“text/plain”) mismatch (X-Content-Type-Options: nosniff).

[issues](https://sentry.example.de/organizations/suv/exampleorg/)

[sentry] Instrumenting session with rrweb [bootstrap.tsx:69:12](webpack:///app/bootstrap.tsx)

GET https://sentry.example.de/_static/1620640325/sentry/js/ads.js [HTTP/2 404 Not Found 291ms]

The resource from “https://sentry.example.de/_static/1620640325/sentry/js/ads.js” was blocked due to MIME type (“text/plain”) mismatch (X-Content-Type-Options: nosniff).

[issues](https://sentry.example.de/organizations/exampleorg/issues/)

12:43:58.234 Loading failed for the <script> with source “https://sentry.example.de/_static/1620640325/sentry/js/ads.js”. [issues:46:1](https://sentry.example.de/organizations/exampleorg/issues/)
12:44:00.311 Uncaught (in promise) CancelledError: GET /organizations/exampleorg/tags/ 0

Is there somewhere a complete nginx reverse proxy example? Can’t find this in the docs.

That looks like your reverse proxy is not passing mime-type headers along or mangles them for some reason. Don’t think this is related to Sentry itself at all.

We don’t have this as it is beyond Sentry’s scope. There are much better and well-maintained tutorials out there for setting up Nginx as a reverse proxy for any service.

Sure, how to setup nginx as reverse proxy is no big deal. But some applications need some special headers to work. And these we can’t guess. Are there any headers the reverse proxy should set in order that sentry will work properly?

Thanks!

Nope :slight_smile:

Same Problem here with Chrome 90. Firefox still works fine.
No changes to Sentry or reverse proxy itself done …