Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[NextJs] New DSNs with the .us in the host does not work tunnelRoute option #10948

Closed
3 tasks done
Fwang36 opened this issue Mar 6, 2024 · 1 comment
Closed
3 tasks done
Labels
Package: nextjs Issues related to the Sentry Nextjs SDK Type: Bug

Comments

@Fwang36
Copy link
Member

Fwang36 commented Mar 6, 2024

Is there an existing issue for this?

How do you use Sentry?

Sentry Saas (sentry.io)

Which SDK are you using?

@sentry/nextjs

SDK Version

7.105

Framework Version

12.2.2

Link to Sentry event

No response

SDK Setup

No response

Steps to Reproduce

New DSNs have .us in the host. This causes the tunnelRoute option in next.config.js not to run.

Workaround is to remove the .us from the DSN

Ex. change the .ingest.us.sentry.io portion of the DSN to .ingest.sentry.io

Expected Result

tunnelRoute should be rewriting DSNs that have the .us

Actual Result

  Sentry.init({
    dsn: "https://[email protected]/4504089864830976",

  })
sentry: {
  tunnelRoute: "/monitoring"
}
Screenshot 2024-03-06 at 10 53 32 AM

Removing the .us -

  Sentry.init({
    dsn: "https://[email protected]/4504089864830976",

  })
sentry: {
  tunnelRoute: "/monitoring"
}
Screenshot 2024-03-06 at 10 54 43 AM
@AbhiPrasad
Copy link
Member

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Package: nextjs Issues related to the Sentry Nextjs SDK Type: Bug
Projects
Archived in project
Development

No branches or pull requests

3 participants