Sentry-javascript: uBlock Origin blocks requests to sentry.io

[piotr-cz]

• [x] Review the documentation: https://docs.sentry.io/
• [x] Search for existing issues: https://github.com/getsentry/sentry-javascript/issues
• [x] Use the latest release: https://github.com/getsentry/sentry-javascript/releases
• [ ] Provide a link to the affected event from your Sentry account

Package + Version

• [x] @sentry/browser
• [ ] @sentry/node
• [ ] raven-js
• [ ] raven-node _(raven for node)_
• [ ] other:

Version:

5.23.0

Description

The uBlock Origin (probably most popular adblocking extension, installed by default on Raspberry PI Chromium) recently added sentry.io to it's _uBlock filters - privacy_ list on 28/08/2020.

As a result, Sentry events are not being sent to server.

Log from from Chrome DevTools console:

https://xxx.ingest.sentry.io/api/xxx/store/?sentry_key=xxx&sentry_version=7
net::ERR_BLOCKED_BY_CLIENT

The sentry.io entry might have been added to the list as a result of grofers.com (mis)using it to track user behaviour, unfortunately affecting web apps on all domains.

Reference to commit: https://github.com/uBlockOrigin/uAssets/commit/6489ab5eaf2a838bcdf2ae74ec8542ebb897d16d

[piotr-cz]

Related PR in uBlock/uAssets repo: https://github.com/uBlockOrigin/uAssets/pull/7924

[lobsterkatie]

Hey, @piotr-cz, thanks for reporting this. We’re aware of it, and don't yet have a solution, but we'll update here once we do.

[piotr-cz]

This issue causes using Sentry's javascript platform useless in our product, as our web app is currently being deployed _only_ to machines with uBlock Origin extension enabled (Raspberry PI).

Are there any special directions for setting up a forward proxy for @sentry/browser package?

[jan-auer]

@piotr-cz We have something in our works for this. Would you be comfortable with running a small service on your domain that redirects events to Sentry? If so, please reach out to me via jan.[email protected]. Thanks!

[piotr-cz]

This seems to be resolved by https://github.com/uBlockOrigin/uAssets/commit/9ab563e5fb6c2c8be78aa1ac47e429e057a0ead0, at least for now.

Thank you for everyone involved.

[hyperknot]

Now Easyprivacy is doing it, I've opened an issue here:
https://github.com/easylist/easylist/issues/6963

[piotr-cz]

Oh no, not again

[hyperknot]

Easylist's official reply: "Happy to keep it. We block event, error trackers."

I guess this means all uBlock Origin users (where Easylist privacy is default) are not working with Sentry. I don't know if the same list is used by any other blocker, but this means the Sentry team needs to look for a proxy solution.

[brpaz]

@hyperknot Can confirm, that sentry is not working for me with ublock installed as today.

[piotr-cz]

@hyperknot I suggest you open new Issue concerning https://github.com/easylist/easylist/issues/6963.
This issue is closed as it's been resolved in uBlock Origin repo and in effect problem you describe may not get enough attention here.

[leocharrua]

Hello, I have the same issue with uBlock Origin ... Blocks sentry:

o265477.ingest.sentry.io/api/5459967/envelope/?sentry_key=XXXXXX&sentry_version=7:1 Failed to load resource: net::ERR_BLOCKED_BY_CLIENT

I don't wanna tell to my clients that uninstall uBlock Origin.

Can you help me?

Thanks

[kamilogorek]

@leocharrua https://docs.sentry.io/platforms/javascript/troubleshooting/#dealing-with-ad-blockers

[hyperknot]

This page doesn't provide information about how to avoid blocking the "ingest" part. For that you need an external service in Docker for example.

[leocharrua]

Hello. I am using the the SDK package directly through the npm:

 "@sentry/angular": "^5.28.0",
"@sentry/tracing": "^5.28.0",

In main.ts (ionic/angular):

import * as Sentry from '@sentry/angular';
import { Integrations } from '@sentry/tracing';

Sentry.init({
dsn: 'https://[email protected]/545xxxx',
integrations: [
new Integrations.BrowserTracing({
routingInstrumentation: Sentry.routingInstrumentation,
}),
],

tracesSampleRate: 1.0,
});

This is the "ingest" part I suppose.

We don't use Docker ... any other ideas? The uBlock Origin team can do anything?

Thanks

[lobsterkatie]

@leocharrua There is discussion of proxying in this issue, which helps with the outbound (ingest) blocking. Also, please feel free to add your voice to https://github.com/easylist/easylist/issues/6963, or, as @piotr-cz says, open a new issue there. This has come up before with them and other ad blockers, and has been eventually resolved each time, but more support in favor of fixing it this time certainly can't hurt.