NextJS SDK - failing to enable release health / pass user ip to Sentry

[Branch]

NextJS & Sentry (NextJS) SDK versions:
NextJS: 13.1.1 (pages router)
sentry/nextjs: 7.86.0

Description

Hi,

I'm a Sentry beginner and have been tinkering with it for the last couple of days using the NextJS SDK.

It seems to be mostly working as it should out of the box. However, I struggle to enable "Release health".

I'm publishing releases just fine using Github actions. These appear in the Sentry UI as well as any issues caught in my app. However, users remain at 0. I believe that this is the cause of release health being disabled since I have no users reported. As far as I can understand, the user ip should be sent by default from the app to Sentry, which it isn't. Therefore I'm getting no users.

After having added the RequestData integration to the server and edge configs, it sends the ip to Sentry. However the ip is set to localhost (127.0.0.1).

Looking at the request headers within the issue, I can see that X-Forward-For holds the correct client ip.

When reading discussions / tutorials regarding how to set this up I get the feeling that this should all happen by default, but maybe I'm wrong here.

Configs

My server (and edge) configs looks as follows:

Sentry.init({
    release: process.env.NEXT_PUBLIC_CONFIG_BUILD_ID,
    environment: process.env.SENTRY_ENV,
    dsn: process.env.SENTRY_DSN,
    tracesSampleRate: 1,
    debug: false,
    integrations: [
        new Sentry.Integrations.RequestData({
            include: {
                ip: true,
            },
        }),
    ],
})

My client cfg looks as follows:

Sentry.init({
    release: process.env.NEXT_PUBLIC_CONFIG_BUILD_ID,
    environment: process.env.SENTRY_ENV,
    dsn: process.env.SENTRY_DNS,
    // 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,
})

The sentry part of my nextjs config looks as follows:

webpack: (config, { webpack, buildId }) => {
       ...
            config.plugins.push(
                new webpack.DefinePlugin({
                    __SENTRY_DEBUG__: false,
                    __SENTRY_TRACING__: false,
                    __RRWEB_EXCLUDE_IFRAME__: true,
                    __RRWEB_EXCLUDE_SHADOW_DOM__: true,
                    __SENTRY_EXCLUDE_REPLAY_WORKER__: true,
                })
            )
        }
        return config
    },

...
module.exports = withSentryConfig(
              nextConfig,
              {
                  silent: true,
                  org: 'my-org',
                  project: process.env.SENTRY_PROJECT,
                  release: nextBuildId.sync({ dir: __dirname, describe: true }),
              },
              {
                  widenClientFileUpload: true,
                  transpileClientSDK: false,
                  hideSourceMaps: true,
                  disableLogger: true,
              }
)

I'm probably missing something obvious, and I'm sorry if that's the case. I just can't seem to figure this out.

[Branch]

As suspected, I had missed something obvious.

This was related to spelling errors in env variables as well as env variables not being publicly available to the client.