Solution skill
Sentry: browser events vanish, server events arrive
Complete solution
Shows how to fix sentry: browser events vanish, server events arrive. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
Use it when your issue stream is full of errors from code you did not ship. Adblockers and privacy extensions block requests to known ingest hosts (*.ingest.sentry.io). Your SDK is working; the network never lets the envelope leave the browser. This also skews every client metric: error rates, web vitals, and replay counts all read low.
When to use
You are seeing this: Server-side issues flow normally. Use this skill when you run into "Sentry: browser events vanish, server events arrive".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
The symptom
Server-side issues flow normally. Client-side issues are undercounted or absent entirely, with no SDK errors. The gap is biggest among privacy-conscious users and in regions where filter lists are aggressive.
The cause
Adblockers and privacy extensions block requests to known ingest hosts (*.ingest.sentry.io). Your SDK is working; the network never lets the envelope leave the browser. This also skews every client metric: error rates, web vitals, and replay counts all read low.
The fix: tunnel through your server
// next.config.ts
withSentryConfig(nextConfig, {
tunnelRoute: "/sentry-tunnel",
});The tunnel route makes event POSTs look first-party, which filter lists do not block. For non-Next.js apps, proxy /sentry-tunnel (or any path) to your ingest host at the edge or in your server framework, and point the SDK's tunnel option at it.
Confirmation
Compare event counts with and without an adblocker in a test browser. If events arrive clean and vanish blocked, it is the filter list, not your code. Also check that the tunnel route itself is not behind auth middleware rejecting the POSTs, which produces the same symptom from the other direction.
Related: extension noise
The reverse problem is browser extensions INJECTING errors into your stream. denyUrls/allowUrls filter by script origin, and thirdPartyErrorFilterIntegration (bundler builds only, needs the applicationKey build option) drops or tags errors from unmarked third-party frames. Use it when your issue stream is full of errors from code you did not ship.
Evidence
Researched against live Sentry docs 2026-09-26. The Next.js guide (docs.sentry.io/platforms/javascript/guides/nextjs/) documents withSentryConfig tunnelRoute /sentry-tunnel with the description Route Sentry requests through your server (avoids ad-blockers). The JS filtering page (docs.sentry.io/platforms/javascript/configuration/filtering/) documents allowUrls/denyUrls and the thirdPartyErrorFilterIntegration for browser-extension noise, noting the integration does not work with the loader script or CDN bundles.
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_wiQeQNXQY7FidR4IKeSjRw" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Sentry: browser events vanish, server events arrive <span>— Vectle</span></a>