Reverse proxy setup for MC and TS3 servers on a subdomain using standard ports
Reverse proxy setup for MC and TS3 servers on a subdomain using standard ports
Hey everyone, I’m trying to set up separate subdomains for different MC and TS3 servers while keeping the standard ports in use. Right now I use Nginx Proxy Manager with Proxy Hosts for my web servers that have subdomains, which works perfectly (like nextcloud.domain.com or plex.domain.com). For the games servers, I also rely on Nginx Proxy Manager but with the Stream feature. However, I’m stuck because I can’t assign subdomains to the same ports for multiple servers—each server needs its own port. My current configuration: mc1.domain.com → 1st MC Server - Port 25565; mc2.domain.com → 2nd MC Server - Port 25565; mc3.domain.com → 3rd MC Server - Port 25565. I’d like to replicate this for my TS3 servers in the same way: mc1.domain.com → TS3 Server - Port 25565, etc. Any suggestions or alternatives would be super helpful!
The issue lies in the fact that the FQDN appears in HTTP requests, allowing you to operate several web servers on the same IP and port combination. This provides more data than just an IP and port. There are two approaches: First, set up your own network by linking each FQDN to a unique IP address, assigning all IPs to the same server machine. Then run each server daemon instance on different IPs but the same port, using a local DNS or modifying host files. Second, instead of giving multiple IPs to the server itself, direct them through a router. The router handles translating IP:port pairs—for example, mc1.domain.com resolves to 10.0.0.5, while mc2.domain.com maps to 10.0.0.6, and so on. For external access, both methods require several public IPs or a VPN server for users outside your network to connect and use your DNS resolution. *This could also apply with IPv6.*
Thanks for the response! I'll check the issue with the single static IPv4 address.