Reinstating ability to select what port ranges the web interfaces bind to or alternative enabling choosing port when creating instance.

[Cixxar]

I confirm that

• [X] I have searched for an existing feature request matching the description.

Feature Description

In earlier versions it was possible to set a range the instances webinterface would use, both excluding it from the ports game servers used but also setting a range to go from in auto increments.

This feature is key for us when running an environment where we have to have the interfaces using specific ports. currently the work around for new instances is to rebind the interface after but since this feature was available earlier then it can be assumed it is able to be re-enabled again.

as an alternative, having the option to chose the web-interface port when creating a game server would be workable.

With Respect. Cix

[IceOfWraith]

What's the use case where the interface requires a specific port?

[Cixxar]

Hi Ice,

we would say any case on windows server 2019 where the hardcoded start port range for webinterfaces interfere with operations of all other systems(service,system,program,connection and so on) on that port Since the hardcoded port defaults to 8080 is causes issues on services/systems that are currently using that port that are not a part of AMP. since 8080 is used as a default port for many things we have needed to change it for serveral systems we are using - basically, we have everything from 8080 to 8097 on lock for other systems. we are seeing that either the system using that port wont work or Webinterface wont work until the webinterface port is rebind using console commands. it do not take too long to rebind but it causes down time on that system leading to interruptions and complains from users.

[IceOfWraith]

You just need to remove that range from the Application Port Ranges in AMP then. Then AMP will only grab outside those ports.

[BroOtti]

It would be nice to have a separated setting for the instances web port again as currently it uses the ports designated to game servers. With IPv6-only I wouldn't mind, but I have only a set range of ports available that are forwarded for IPv4 support and I don't want instances use them up for their web port which is only listening on localhost by design.