I tested the Windows dedicated server now in a proper NAT setup with a single public IP and explicit port forwarding, and honestly I am not happy with what I found.
P2pProxyAddress works for selecting the bind IP, but I could not find any way to force a fixed listen port. I tested multiple variants such as -ServerPort=30000, -Port=30000, -port=30000, ?Port=30000, and ?ListenPort=30000, including launching the shipping binary directly. None of them made the server listen on the requested port.
The server keeps choosing a different local listening port on every start. In my tests it used values like 42027, 42113, 43114, 44041, 44274, 44509, etc. This makes controlled hosting extremely difficult, because classic port forwarding depends on stable ports.
I already confirmed that this is not just a firewall or outbound connectivity issue:
HTTPS to the Windrose backend on port 443 works
TURN/STUN-related connectivity also works
P2pProxyAddress correctly binds the server to the VM's internal IP
So the real issue is simple: the dedicated server appears to ignore any attempt to set a fixed port and instead uses dynamic/random ports.
I do not think this is acceptable for professional hosting or datacenter-style environments. This may be fine for home hosting, but it is not fine for providers or controlled NAT setups where we need predictable network behavior.
What I need from you is::
Is there an officially supported way to force a fixed listen port for the dedicated server?
If yes, what is the exact parameter or config key?
If no, is this going to be fixed?
Right now the server is effectively unsuitable for normal hosted deployment with controlled port forwarding, and that is a serious problem.