[GH-ISSUE #5937] Error in quickstart script for NPM configuration #12449

Open
opened 2026-08-05 02:05:56 -04:00 by saavagebueno · 0 comments
Owner

Originally created by @Tankdoz on GitHub (Apr 21, 2026).
Original GitHub issue: https://github.com/netbirdio/netbird/issues/5937

quickstart script asks wheter container ports should be bound to localhost only:

Should container ports be bound to localhost only (127.0.0.1)?
Choose 'yes' if your reverse proxy runs on the same host (more secure).
Bind to localhost only? [Y/n]:

When answering n (NPM running on a different host), the generated npm-advanced-config.txt still hardcodes 127.0.0.1 in all proxy_pass and grpc_pass directives. The NPM setup instructions also tell the user to use 127.0.0.1 as the forward hostname.
This means the generated config is incorrect and non-functional for anyone running NPM on a separate host.

To Reproduce

  1. Run the quickstart script
  2. Select [3] Nginx Proxy Manager as reverse proxy
  3. Answer n to localhost binding
  4. Inspect generated npm-advanced-config.txt

Expected behavior

When the user answers n to localhost binding, the script should either:

Prompt for the hostname/IP of the reverse proxy host and use it in the generated config, or
Replace 127.0.0.1 with a placeholder like <'YOUR-NETBIRD-HOST-IP'> and add a comment explaining it needs to be changed

Are you using NetBird Cloud?

no

NetBird version

Management
v0.69.0
Dashboard
v2.36.0

Is any other VPN software installed?

no

Debug output

N/A

Originally created by @Tankdoz on GitHub (Apr 21, 2026). Original GitHub issue: https://github.com/netbirdio/netbird/issues/5937 quickstart script asks wheter container ports should be bound to localhost only: ``` Should container ports be bound to localhost only (127.0.0.1)? Choose 'yes' if your reverse proxy runs on the same host (more secure). Bind to localhost only? [Y/n]: ``` When answering **_n_** (NPM running on a different host), the generated npm-advanced-config.txt still hardcodes 127.0.0.1 in all proxy_pass and grpc_pass directives. The NPM setup instructions also tell the user to use 127.0.0.1 as the forward hostname. This means the generated config is incorrect and non-functional for anyone running NPM on a separate host. **To Reproduce** 1. Run the quickstart script 2. Select [3] Nginx Proxy Manager as reverse proxy 3. Answer n to localhost binding 4. Inspect generated npm-advanced-config.txt **Expected behavior** When the user answers n to localhost binding, the script should either: Prompt for the hostname/IP of the reverse proxy host and use it in the generated config, or Replace 127.0.0.1 with a placeholder like <'YOUR-NETBIRD-HOST-IP'> and add a comment explaining it needs to be changed **Are you using NetBird Cloud?** no **NetBird version** Management v0.69.0 Dashboard v2.36.0 **Is any other VPN software installed?** no **Debug output** N/A
saavagebueno added the triage-needed label 2026-08-05 02:05:56 -04:00
Sign in to join this conversation.
No Label triage-needed
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: DYNR/netbird#12449