I am using newt binaries installed with curl -fsSL https://static.pangolin.net/get-newt.sh | bash
Whenever I run newt on the CLI with the --port flag it does not seem to be taken into account, but still selects one port at random.
This prevents me from forwarding the port to avoid relay connections (as any restart of newt would result in a new port being selected).
Environment
OS Type & Version: Debian 13
Pangolin Version: 1.15.4
Gerbil Version: 1.3.0
Traefik Version: 3.6
Newt Version: 1.10.0 (was also not working on 1.9.0)
Olm Version: N/A
To Reproduce
Run newt --port 55500 --id ID --secret SECRET --endpoint https://pangolin.my.domain , connect to the client via Pangolin ios app. Random port is selected (visible in the Status --> Sites tab)
Expected Behavior
Clients connect on port 55000
Originally created by @serguma88 on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/fosrl/newt/issues/243
### Describe the Bug
I am using newt binaries installed with `curl -fsSL https://static.pangolin.net/get-newt.sh | bash`
Whenever I run newt on the CLI with the `--port` flag it does not seem to be taken into account, but still selects one port at random.
This prevents me from forwarding the port to avoid relay connections (as any restart of newt would result in a new port being selected).
### Environment
- OS Type & Version: Debian 13
- Pangolin Version: 1.15.4
- Gerbil Version: 1.3.0
- Traefik Version: 3.6
- Newt Version: 1.10.0 (was also not working on 1.9.0)
- Olm Version: N/A
### To Reproduce
Run `newt --port 55500 --id ID --secret SECRET --endpoint https://pangolin.my.domain` , connect to the client via Pangolin ios app. Random port is selected (visible in the Status --> Sites tab)
### Expected Behavior
Clients connect on port 55000
@AntonVonDelta commented on GitHub (Feb 25, 2026):
This bug also affects me. It looks like it uses the port for some traffic at container start and some nat hole punching it seems but then it stops using it. I managed to fix nat hole punching by enabling static port in opensense for outbound traffic but exposing this port together with using --port did not work at all
<!-- gh-comment-id:3959249054 -->
@AntonVonDelta commented on GitHub (Feb 25, 2026):
This bug also affects me. It looks like it uses the port for some traffic at container start and some nat hole punching it seems but then it stops using it. I managed to fix nat hole punching by enabling static port in opensense for outbound traffic but exposing this port together with using --port did not work at all
<!-- gh-comment-id:3994457199 -->
@oschwartz10612 commented on GitHub (Mar 4, 2026):
I fixed this in 7920295b8c9a955faaecc5dddd7c6f2f485398c1
doing a release shortly
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @serguma88 on GitHub (Feb 24, 2026).
Original GitHub issue: https://github.com/fosrl/newt/issues/243
Describe the Bug
I am using newt binaries installed with
curl -fsSL https://static.pangolin.net/get-newt.sh | bashWhenever I run newt on the CLI with the
--portflag it does not seem to be taken into account, but still selects one port at random.This prevents me from forwarding the port to avoid relay connections (as any restart of newt would result in a new port being selected).
Environment
To Reproduce
Run
newt --port 55500 --id ID --secret SECRET --endpoint https://pangolin.my.domain, connect to the client via Pangolin ios app. Random port is selected (visible in the Status --> Sites tab)Expected Behavior
Clients connect on port 55000
@AntonVonDelta commented on GitHub (Feb 25, 2026):
This bug also affects me. It looks like it uses the port for some traffic at container start and some nat hole punching it seems but then it stops using it. I managed to fix nat hole punching by enabling static port in opensense for outbound traffic but exposing this port together with using --port did not work at all
@serguma88 commented on GitHub (Feb 28, 2026):
Issue still seems to be there in 1.10.1, flag gets completely ignored, debug logs don't even show any kind of error:
@oschwartz10612 commented on GitHub (Mar 4, 2026):
I fixed this in
7920295b8cdoing a release shortly