wings configure generates an invalid configuration for reverse-proxied nodes

Current Behavior

I am running Wings behind a reverse proxy (Plesk/Nginx).

The node is configured in the Panel with:

• Communicate Over SSL: Yes
• Behind Proxy: Yes
• FQDN: node.lexian.dev
• Daemon Port: 443

Plesk terminates HTTPS on port 443 and proxies requests to Wings on an internal port (127.0.0.1:55575).

When I run wings configure (or allow the Panel to push a configuration update), the generated configuration causes Wings to bind directly to port 443 instead of the internal port.

Since Plesk is already listening on port 443, Wings fails to start with:

listen tcp 0.0.0.0:443: bind: address already in use

This means I cannot use wings configure with a reverse-proxied deployment without manually editing the generated configuration.

Expected Behavior

When a node is configured as being behind a proxy, I would expect Wings to support a different internal bind port from the public daemon port.

The Panel should continue communicating with:

https://node.lexian.dev:443

while Wings should be able to listen on an internal port (for example 127.0.0.1:55575) behind the reverse proxy.

If this is not currently supported, I would expect wings configure to either preserve an existing custom bind port or provide a way to specify one instead of always binding to the public daemon port.

Steps to Reproduce

1. Configure a reverse proxy (Plesk/Nginx) to expose Wings over HTTPS on port 443.
2. Configure the proxy to forward requests to Wings on an internal port (e.g. 127.0.0.1:55575).
3. In the Panel:
   • Enable "Communicate Over SSL"
   • Enable "Behind Proxy"
   • Set the daemon port to 443.
4. Run wings configure.
5. Start Wings.

Wings attempts to bind to port 443 instead of the internal port, causing it to fail because the reverse proxy already owns port 443.

Panel Version

1.14.1

Wings Version

1.13.1

Games and/or Eggs Affected

N/A

Docker Image

N/A

Error Logs

listen tcp 0.0.0.0:443: bind: address already in use

Is there an existing issue for this?

• I have searched the existing issues before opening this issue. I understand that maintainers may close this issue without communication if I have not provided sufficient information.