Skip to content

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

@Fwang36

Description

@Fwang36

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    Package: nextjsIssues related to the Sentry Nextjs SDK

    Type

    Projects

    Status

    No status

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions