Skip to content

fix: restore Sentry tunnel route to bypass ad blockers#17285

Merged
sergical merged 5 commits intomasterfrom
fix/restore-tunnel-route
Apr 9, 2026
Merged

fix: restore Sentry tunnel route to bypass ad blockers#17285
sergical merged 5 commits intomasterfrom
fix/restore-tunnel-route

Conversation

@sergical
Copy link
Copy Markdown
Member

@sergical sergical commented Apr 8, 2026

DESCRIBE YOUR PR

Re-adds tunnelRoute: '/monitoring' to withSentryConfig in next.config.ts. This was removed in #9152 during the changelog domain switch and never restored.

Without it, ad blockers silently block all browser-side Sentry requests (errors, replays, user feedback) from reaching ingest.sentry.io. The tunnel routes these through our own origin at /monitoring, bypassing ad blockers.

This also fixes the User Feedback widget (DocFeedback component) silently failing — users see "Thanks for your feedback" but nothing is delivered when an ad blocker is active.

IS YOUR CHANGE URGENT?

  • Urgent deadline (GA date, etc.):
  • Other deadline:
  • None: Not urgent, can wait up to 1 week+

PRE-MERGE CHECKLIST

  • Checked Vercel preview for correctness, including links
  • PR was reviewed and approved by any necessary SMEs
  • PR was reviewed and approved by a member of the Sentry docs team

Re-adds `tunnelRoute: '/monitoring'` which was accidentally removed in #9152
during the changelog domain switch. Without it, ad blockers silently block
all Sentry requests (errors, feedback, replays) from reaching ingest.sentry.io.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@vercel
Copy link
Copy Markdown

vercel bot commented Apr 8, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
sentry-docs Ready Ready Preview, Comment Apr 9, 2026 2:08pm
1 Skipped Deployment
Project Deployment Actions Updated (UTC)
develop-docs Ignored Ignored Preview Apr 9, 2026 2:08pm

Request Review

Copy link
Copy Markdown
Contributor

@cursor cursor bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Cursor Bugbot has reviewed your changes and found 2 potential issues.

Fix All in Cursor

❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, enable autofix in the Cursor dashboard.

Reviewed by Cursor Bugbot for commit 0aea4c5. Configure here.

…15/16

The tunnel route exclusion docs only referenced proxy.ts, which is the
Next.js 16 filename. Users on Next.js 15 need middleware.ts instead.
Clarify both filenames since the page covers Next.js 15+.

Co-Authored-By: Claude <noreply@anthropic.com>
Copy link
Copy Markdown
Member

@logaretm logaretm left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Like Charly said, this is a whack-a-mole game but we have no real solution for it so 🤷‍♂️

@sergical sergical merged commit df7a8be into master Apr 9, 2026
20 checks passed
@sergical sergical deleted the fix/restore-tunnel-route branch April 9, 2026 15:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants