-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
[NextJs] New DSNs with the .us in the host does not work tunnelRoute option #10948
Copy link
Copy link
Closed
Labels
Description
Is there an existing issue for this?
- I have checked for existing issues https://github.com/getsentry/sentry-javascript/issues
- I have reviewed the documentation https://docs.sentry.io/
- I am using the latest SDK release https://github.com/getsentry/sentry-javascript/releases
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://fd28336e6c92410386c2ffffe4d3b7c2@o1407376.ingest.us.sentry.io/4504089864830976",
})
sentry: {
tunnelRoute: "/monitoring"
}
Removing the .us -
Sentry.init({
dsn: "https://fd28336e6c92410386c2ffffe4d3b7c2@o1407376.ingest.sentry.io/4504089864830976",
})
sentry: {
tunnelRoute: "/monitoring"
}

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Fields
Give feedbackNo fields configured for issues without a type.
Projects
Status
No status