Managing forwarded ports
Managing forwarded ports
Port Forwarding plans let you choose exactly which external ports reach your server, and which internal port they land on.
Adding a port
From your service page, open Manage & connect, then the port forwarding section. Fill in:
- Protocol โ TCP, UDP, or both
- External port โ the port the outside world connects to on your shared IP
- Your server's port โ where it actually lands on your machine (can be the same number, or different)
- A port range instead of a single port, if you need several consecutive ports at once
A description field is optional but helps you remember which rule is which once you have several.
Port limits
Each plan includes a set number of ports (Starter: 3, Standard: 8, Pro: 20, Business: 60, Ultra: 150). A single port and a 10-port range both count against that total the same way โ by how many ports they use, not how many rules you've created. Need more than your plan includes? Add extra ports as a paid add-on at checkout or via an upgrade, rather than needing to move to a bigger plan.
Why some ports can't be used
A small set of ports are reserved for our own infrastructure (22, 53, 80, 443, 3306, 6379, and a few others) and can't be forwarded โ if you try, you'll get a clear error explaining why.
Conflicts on shared IPs
Port Forwarding plans share one IP across many customers. If the port you want is already in use by someone else's rule on that IP, you'll be asked to pick a different one โ this is checked before the rule is created, so it never silently overwrites someone else's forwarding.
Removing a rule
Click Remove next to any rule on the same management page. It stops forwarding immediately and frees that port for reuse.
Related: What is IP Tunneling & Port Forwarding?.
Was this not what you needed?
Tell us what you're trying to do and our team will help directly.
Open a support ticket Ask on Discord