Sentry events blocked by Brave Shields — fixed via backend proxy

1

Hey everyone :waving_hand:

While testing my React-based web app on Brave, I noticed that Sentry events weren’t getting logged at all, even though everything worked perfectly on Chrome and Firefox.

After checking the Network tab in DevTools, I found this status:
``(blocked:other)```

The requests initiated by @sentry_react were being completely blocked by Brave Shields (see screenshot below :backhand_index_pointing_down:).

image
image650×860 28.2 KB

Root cause:
Brave automatically blocks telemetry and analytics requests to third-party domains like sentry.io for privacy reasons — which is great for users but silently breaks client-side Sentry logging in production apps.

:white_check_mark: My Fix — Backend Proxy (API Tunneling)

My backend securely forwards the payload to Sentry using my project’s DSN — Brave treats it as a first-party request, so it’s no longer blocked.

Sentry.init({
dsn: ‘/api/sentry-proxy’,
tunnel: ‘/api/sentry-proxy’,
integrations: [new BrowserTracing()],
});

Backend (Express / .NET / FastAPI)

app.post('/api/sentry-proxy', async (req, res) => {
  await fetch('https://oXXXX.ingest.sentry.io/api/XXXX/envelope/', {
    method: 'POST',
    headers: req.headers,
    body: req.body,
  });
  res.status(200).end();
});

This approach keeps privacy intact while letting developers capture errors for debugging.
Works seamlessly across Brave, Chrome, Firefox, and Edge :bullseye:

I implemented this fix while building ResumeFreePro.com — a free AI-powered resume builder that helps users create professional, ATS-optimized resumes directly in the browser (no signup or credit card required).

Hope this helps anyone who’s struggling with blocked Sentry events in Brave.
Happy to share full code snippets or setup details if anyone’s interested :raising_hands:

— Abhay

2

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.