Not every service is web. Port forwarding works at Layer 4 (TCP/UDP), forwarding traffic that arrives at a port on your veilx endpoint to the matching port on your origin. It accelerates non-HTTP services and hides your origin's real address.
What port forwarding is
Unlike web acceleration, which works at Layer 7, port forwarding works at Layer 4: it doesn't parse the application protocol, it just passes connections through by port. That lets it carry games, databases, custom TCP/UDP protocols and other non-web traffic, while keeping the origin behind veilx.
Create a forwarding rule
Create a rule under "Port forwarding" in the console, specifying the inbound port, protocol (TCP or UDP), and the origin address and port. After saving, veilx assigns an endpoint, and clients connect to the specified port on it.
Origin and protocol
- The origin needs a valid public IP and port; the source address is validated on creation, and an invalid address won't be saved.
- The protocol must match what the origin actually listens on: choose TCP for TCP services, UDP for UDP.
- One origin can have multiple rules, forwarding services on different ports.
Connect and verify
Once the rule is live, connect a client to the matching port on the veilx endpoint and confirm communication works. Compare connectivity and latency between connecting to the origin directly and through veilx to confirm the forwarding path is healthy.