incessant ERR_INVALID_URL logs on every exception captured

[oalhait]

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.93.0

Framework Version

React 18.2.0, NextJS 14.1.0

Link to Sentry event

https://tabbed-ai.sentry.io/issues/4959896033/?environment=production&project=4506322999640064&query=&referrer=issue-stream&statsPeriod=30d&stream_index=1

SDK Setup

sentry.client.config.ts

// This file configures the initialization of Sentry on the client.
// The config you add here will be used whenever a users loads a page in their browser.
// https://docs.sentry.io/platforms/javascript/guides/nextjs/

import * as Sentry from "@sentry/nextjs";

Sentry.init({
  dsn: "https://fc13b04e9af3e9edfc762f6e67d0dd70@o4506322999508992.ingest.sentry.io/4506322999640064",

  // Adjust this value in production, or use tracesSampler for greater control
  tracesSampleRate: 1,

  // Setting this option to true will print useful information to the console while you're setting up Sentry.
  debug: false,

  replaysOnErrorSampleRate: 1.0,

  // This sets the sample rate to be 10%. You may want this to be 100% while
  // in development and sample at a lower rate in production
  replaysSessionSampleRate: 0.1,

  // You can remove this option if you're not planning to use the Sentry Session Replay feature:
  integrations: [
    new Sentry.Replay({
      // Additional Replay configuration goes in here, for example:
      maskAllText: true,
      blockAllMedia: true,
    }),
  ],

  environment: process.env.STACK_NAME === "Prod" ? "production" : "development",
});

sentry.edge.config.ts

// This file configures the initialization of Sentry for edge features (middleware, edge routes, and so on).
// The config you add here will be used whenever one of the edge features is loaded.
// Note that this config is unrelated to the Vercel Edge Runtime and is also required when running locally.
// https://docs.sentry.io/platforms/javascript/guides/nextjs/

import * as Sentry from "@sentry/nextjs";

Sentry.init({
  dsn: "https://fc13b04e9af3e9edfc762f6e67d0dd70@o4506322999508992.ingest.sentry.io/4506322999640064",

  // Adjust this value in production, or use tracesSampler for greater control
  tracesSampleRate: 1,

  // Setting this option to true will print useful information to the console while you're setting up Sentry.
  debug: false,

  environment: process.env.STACK_NAME === "Prod" ? "production" : "development",
});

sentry.server.config.ts

// This file configures the initialization of Sentry on the server.
// The config you add here will be used whenever the server handles a request.
// https://docs.sentry.io/platforms/javascript/guides/nextjs/

import * as Sentry from "@sentry/nextjs";

Sentry.init({
  dsn: "https://fc13b04e9af3e9edfc762f6e67d0dd70@o4506322999508992.ingest.sentry.io/4506322999640064",

  // Adjust this value in production, or use tracesSampler for greater control
  tracesSampleRate: 1,

  // Setting this option to true will print useful information to the console while you're setting up Sentry.
  debug: false,

  environment: process.env.STACK_NAME === "Prod" ? "production" : "development",
});

next.config.js

/** @type {import('next').NextConfig} */
const nextConfig = {
  webpack: (config, { isServer, nextRuntime, webpack }) => {
    // Avoid AWS SDK Node.js require issue: https://github.com/aws-amplify/amplify-js/issues/11030#issuecomment-1653689367
    if (isServer && nextRuntime === "nodejs")
      config.plugins.push(new webpack.IgnorePlugin({ resourceRegExp: /^aws-crt$/ }));
    return config;
  },
};

// Injected content via Sentry wizard below

const { withSentryConfig } = require("@sentry/nextjs");

module.exports = withSentryConfig(
  nextConfig,
  {
    // For all available options, see:
    // https://github.com/getsentry/sentry-webpack-plugin#options

    authToken: process.env.SENTRY_AUTH_TOKEN,
    // Suppresses source map uploading logs during build
    silent: true,
    org: "tabbed-ai",
    project: "app-tabbed-ai",
  },
  {
    // For all available options, see:
    // https://docs.sentry.io/platforms/javascript/guides/nextjs/manual-setup/

    // Upload a larger set of source maps for prettier stack traces (increases build time)
    widenClientFileUpload: true,

    // Transpiles SDK to be compatible with IE11 (increases bundle size)
    transpileClientSDK: true,

    // Routes browser requests to Sentry through a Next.js rewrite to circumvent ad-blockers (increases server load)
    tunnelRoute: "/monitoring-tunnel",

    // Hides source maps from generated client bundles
    hideSourceMaps: true,

    // Automatically tree-shake Sentry logger statements to reduce bundle size
    disableLogger: true,

    // Enables automatic instrumentation of Vercel Cron Monitors.
    // See the following for more information:
    // https://docs.sentry.io/product/crons/
    // https://vercel.com/docs/cron-jobs
    automaticVercelMonitors: false,
  },
);

Steps to Reproduce

approx 50% of the time when an exception is caught, you can observe a bunch of errors propagating as in the screenshot attached in the 'Actual Result' section. the link to this sentry event is provided above

Expected Result

the url

"https://o:orgid.ingest.sentry.io/api/:projectid/envelope/%3Fhsts=0"

should inject the orgId and projectId correctly, which it is not currently doing

Actual Result

[lforst]

Hi, thanks for writing in. I cannot observe this behaviour in my test application. Would you be able to provide a minimal repo that we can use to replicate this? Thanks!

[yashvesikar]

Hi @lforst!
Thanks for looking into this.

I am working with @oalhait on this issue. We are struggling to produce a reproducible repo with the same issue at the moment but will give it a try again soon. I dug around the code a bit and am wondering if it could be due to a tunnel rewrite rule being configured incorrectly from the server side?

I am not sure but this was one of the few places I remember seeing a similar syntax in the sentry codebase and we have been struggling with getting the tunnel setup to run correctly in our production app. Even with the tunnelRoute configured the requests seem to be going to api/v1/sentry

I am happy to try creating a repro again but that may take a little time.

[lforst]

@yashvesikar absolutely no requests should go to /api/v1/sentry. Is this something you set up? The SDK is definitely not sending requests to that location by itself. If you configured the tunnelRoute option do not set a tunnel value in Sentry.init().

EDIT: Just realized it is probably your tunnelRoute option.

[lforst]

Please try to provide reproduction. You seem to be the only team running into this problem from what I can tell. We haven't received similar reports yet and this feature is out quite a while and on by default.