[AUTH/OIDC] - Issues with the NextAuth URL/Port

[Binary-Ape]

Description

I am running Homepage as a TrueNAS App and was setting up the OIDC authentication (PocketID). I am using Nginx Proxy Manager to handle accessing the webpage.

I have set the HOMEPAGE_EXTERNAL_URL to my NPM hostname as that is what the callback would be.

I am running it on a different port (30054) and looking in the logs I was seeing that it was failing a loopback call to the port 3000 (default port).

▲ Next.js 16.3.0
- Local:         http://[::1]:30054
- Network:       http://[::]:30054
✓ Ready in 0ms
✓ Running next.config took 0.8ms

[2026-08-20T17:18:25.921Z] error: [next-auth][error][CLIENT_FETCH_ERROR] 
https://next-auth.js.org/errors#client_fetch_error fetch failed {
  error: {
    message: 'fetch failed',
    stack: 'TypeError: fetch failed\n' +
      '    at node:internal/deps/undici/undici:15157:13\n' +
      '    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)',
    name: 'TypeError'
  },
  url: 'http://localhost:3000/api/auth/providers',
  message: 'fetch failed'
}

I tried to set HOMEPAGE_ALLOWED_HOSTS - but that threw an error that it was already being set.

Digging around I see that NextAuth supports an environment variable NEXTAUTH_URL - I set this to the same value as HOMEPAGE_EXTERNAL_URL and everything worked immediately.

I unset the NEXTAUTH_URL and checking in the container it seems it is not mapping correctly for some reason.

/app $ echo $NEXTAUTH_URL

/app $ echo $HOMEPAGE_EXTERNAL_URL
https://homepage.XXXX.XXXX

I see in the code that that this Line should be setting the value, so I am not sure why it is not being set on my side

homepage version

v2.0.0

Installation method

Other (please describe above)

Configuration

Environment Variables

HOMEPAGE_AUTH_ENABLED = true
HOMEPAGE_EXTERNAL_URL = https://homepage.xxx.xxx
HOMEPAGE_OIDC_CLIENT_SECRET = XXXXXX
HOMEPAGE_OIDC_CLIENT_ID=XXXXX
HOMEPAGE_OIDC_ISSUER = https://pocketid.xxxx.xxx
HOMEPAGE_AUTH_SECRET = XXXXX
LOG_LEVEL = debug

TrueNAS Settings
Port Bind Mode = Exposed for inter-container
Port = 30054
DNS Namesever = Set to Router

Container Logs

▲ Next.js 16.3.0
- Local:         http://[::1]:30054
- Network:       http://[::]:30054
✓ Ready in 0ms
✓ Running next.config took 0.8ms

[2026-08-20T17:18:25.921Z] error: [next-auth][error][CLIENT_FETCH_ERROR] 
https://next-auth.js.org/errors#client_fetch_error fetch failed {
  error: {
    message: 'fetch failed',
    stack: 'TypeError: fetch failed\n' +
      '    at node:internal/deps/undici/undici:15157:13\n' +
      '    at process.processTicksAndRejections (node:internal/process/task_queues:103:5)',
    name: 'TypeError'
  },
  url: 'http://localhost:3000/api/auth/providers',
  message: 'fetch failed'
}

Browser Logs

No response

Troubleshooting

I checked the logs and have output the required information configuration and issues.

[shamoon]

I think this is a somewhat sneaky issue when the port is non-default (and not in docker), I think I have an idea how to handle this, thanks.

[shamoon]

This should be fixed in our next release which I will release soon. If youre able to test that now it would be helpful

[mmomjian]

I have the same issue. I can test if you have a docker image. FYI I am experiencing this with a non standard port, but it IS in docker

[shamoon]

Thanks, this was released in 2.1.0, but feedback welcome of course

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.

[Binary-Ape]

I can confirm that this is fixed in 2.1.0 for my TrueNAS App/Docker Setup.

Thanks for the quick turn around on it!