Fix: Allow users to specify a bind address for self-hosted Next.js applications #77612
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Allow CI Workflow Run
Note: this should only be enabled once the PR is ready to go and can only be enabled by a maintainer |
9785696 to
5c4a982
Compare
Austin1serb
approved these changes
Mar 31, 2025
|
@ijjk is there anything required to get the CI to pass? I noticed it doesn't pass validation due to the old |
ijjk
reviewed
Apr 28, 2025
| @@ -1713,7 +1713,7 @@ process.env.NODE_ENV = 'production' | |||
| process.chdir(__dirname) | |||
|
|
|||
| const currentPort = parseInt(process.env.PORT, 10) || 3000 | |||
| const hostname = process.env.HOSTNAME || '0.0.0.0' | |||
| const hostname = process.env.BIND_ADDRESS || process.env.HOSTNAME || '0.0.0.0' | |||
There was a problem hiding this comment.
Lets add this env variable in the docs as well so users are aware of it https://github.com/ijjk/next.js/blob/canary/docs/01-app/05-api-reference/05-config/01-next-config-js/output.mdx#L54
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
This change adds the ability for users to specify a bind address for self-hosted Next.js apps. By default, if a hostname is set, Next.js will bind to the hostname's loopback address. This becomes problematic within a Kubernetes environment.
Why?
When self-hosting a Next.js application on Kubernetes, it will automatically listen on the pod's private IP address. This causes an issue with Kubernetes port-forwarding, it's not possible to forward requests to the Next.js container. For example, attempting to port-forward to a container will result in the following error:
A workaround for this is to either set the HOSTNAME to an empty string in the Dockerfile or in the Kubernetes deployment.
How?
Allowing the user to specify the bind address provides a cleaner approach to this problem. The pod retains its hostname, and the user can configure Next.js to listen on all interfaces within a Kubernetes environment. This is useful when a user wants to troubleshoot an issue without having to setup an ingress controller.