Prerequisites
Describe the Feature Request
Add an option when creating/editing a device in StartTunnel to select which external IP should be associated with that device. This would allow users with multiple public IPs (e.g., via reserved IPs) to run multiple StartOS servers through a single StartTunnel instance, each with independent port 443 access.
Describe the Use Case
When running multiple StartOS servers through a single StartTunnel instance, each server's services need to be reachable on separate public IPs so that port 443 (and other ports) can be independently forwarded to each server.
Currently, StartTunnel allows configuring port forwards with different external IPs (e.g., the droplet's primary IP and a Digital Ocean Reserved IP), but the WireGuard configuration generated for each device always uses the droplet's primary IP as the WAN IP. There is no option to assign a specific external IP to a specific device/peer.
On the StartOS side, the WAN IP shown in the gateway configuration is derived from the WireGuard config downloaded from StartTunnel, and it cannot be overridden. This appears to prevent clearnet traffic from working when routed through a secondary IP, even though the iptables port forwards are correctly in place.
Describe Preferred Solution
No response
Describe Alternatives
No response
Anything else?
No response
Prerequisites
Describe the Feature Request
Add an option when creating/editing a device in StartTunnel to select which external IP should be associated with that device. This would allow users with multiple public IPs (e.g., via reserved IPs) to run multiple StartOS servers through a single StartTunnel instance, each with independent port 443 access.
Describe the Use Case
When running multiple StartOS servers through a single StartTunnel instance, each server's services need to be reachable on separate public IPs so that port 443 (and other ports) can be independently forwarded to each server.
Currently, StartTunnel allows configuring port forwards with different external IPs (e.g., the droplet's primary IP and a Digital Ocean Reserved IP), but the WireGuard configuration generated for each device always uses the droplet's primary IP as the WAN IP. There is no option to assign a specific external IP to a specific device/peer.
On the StartOS side, the WAN IP shown in the gateway configuration is derived from the WireGuard config downloaded from StartTunnel, and it cannot be overridden. This appears to prevent clearnet traffic from working when routed through a secondary IP, even though the iptables port forwards are correctly in place.
Describe Preferred Solution
No response
Describe Alternatives
No response
Anything else?
No response