Application support
HTTP(S), mail, IRC and many game services can run behind X4B. The appropriate connection method depends on the application's protocols, outgoing connections and need to see original client addresses.
Most TCP and UDP services can work with an appropriate connection method. Examples include:
- HTTP(S) servers: website setup.
- Mail services (POP, SMTP and IMAP): SMTP setup.
- IRC.
- Minecraft and other game servers such as HLDS.
- MangOS/TrinityCore using a GRE tunnel with Linux or a MikroTik router.
- Habbo emulators: version-specific considerations.
- FTP.
Check the application's version and protocol requirements before choosing a reverse proxy or tunnel. Client-IP forwarding requires application support; ordinary TCP/UDP reverse-proxy forwarding presents the proxy address. Tunnels can preserve the client address. Contact support if your application has a client-IP forwarding mechanism that needs configuration.
Port availability
Individual forwarding rules, port ranges and automatic FTP data connections have different constraints. The Dashboard validates the rules available for your service.
Configured TCP and UDP port ranges are limited to 80–45000. Individual UDP ports above 45000 are unavailable through the ordinary customer configuration. Some individual ports below 80 require administrator approval; an allowed individual port does not imply that an enclosing range is allowed.
For passive FTP, follow the FTP-specific setup, including the distinction between automatic data forwarding and manually configured port ranges.
Additional unavailable ports
UDP ports greater than 45,000
TCP ports greater than 50,000 (and 45,000 in certain locations)
Budget locations may have certain uncommon, commonly attacked ports filtered or blocked.
