Skip to content

Guides · VPS

Firewall · ports

All inbound TCP is open by default.

1. Defaults

DirectionStatus
Inbound TCPAll ports forwarded directly to the VPS (80 · 443 · 25565, etc.)
Inbound UDPNot supported
Outbound connectionsAllowed · mail ports 25 · 465 · 587 blocked

Start a program listening on a port to reach it from outside. No additional forwarding needed.

2. Store Firewall tab (restrict inbound traffic)

  1. Service page → Firewall → Add rule.
  2. Port · End port (for a range) · Source IPv4 / CIDR (empty = everyone).
  3. Added or deleted rules take effect within a minute.
  • Once any rule exists, all unlisted ports are blocked. Add every port you use.
  • Deleting all rules allows all TCP ports again.
  • Up to 20 rules · TCP only.
  • Without port 22, SSH is blocked. The web console works independently of this firewall.
ExamplePortSource
SSH from home only22Your public IP (e.g. 203.0.113.7)
Website80 · 443Empty
Minecraft25565Empty
Game port range30000 ~ 30100Empty

Your home IP can change. Use the web console or update the store rules if it does.

3. Guest firewall (optional)

OSCommand
Ubuntu · Debian (ufw)ufw allow 22/tcp → ufw allow 80/tcp → ufw enable
Rocky · CentOS (firewalld)firewall-cmd --permanent --add-port=8080/tcp → firewall-cmd --reload

Before ufw enable, allow port 22 first. Ports published by Docker bypass ufw rules (Docker).

4. If you cannot connect

  1. On the server: ss -tlnp → check for 0.0.0.0:PORT or *:PORT. 127.0.0.1 is unreachable from outside.
  2. Check the guest firewall (ufw · firewalld).
  3. Check the store Firewall rules.
  4. From your PC: Windows Test-NetConnection PUBLIC_IP -Port 80 · Mac nc -vz PUBLIC_IP 80.

Programs requiring inbound UDP (voice servers, some game servers and WireGuard servers) are unsupported.

All guides VPS plans Contact support