ガイド · VPS
ファイアウォール · ポート
受信の TCP は初期状態ですべて開放。
1. Defaults
| Direction | Status |
|---|---|
| Inbound TCP | All ports forwarded directly to the VPS (80 · 443 · 25565, etc.) |
| Inbound UDP | Not supported |
| Outbound connections | Allowed · 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)
- Service page → Firewall → Add rule.
- Port · End port (for a range) · Source IPv4 / CIDR (empty = everyone).
- 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.
| Example | Port | Source |
|---|---|---|
| SSH from home only | 22 | Your public IP (e.g. 203.0.113.7) |
| Website | 80 · 443 | Empty |
| Minecraft | 25565 | Empty |
| Game port range | 30000 ~ 30100 | Empty |
Your home IP can change. Use the web console or update the store rules if it does.
3. Guest firewall (optional)
| OS | Command |
|---|---|
| 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
- On the server:
ss -tlnp→ check for0.0.0.0:PORTor*:PORT.127.0.0.1is unreachable from outside. - Check the guest firewall (ufw · firewalld).
- Check the store Firewall rules.
- From your PC: Windows
Test-NetConnection PUBLIC_IP -Port 80· Macnc -vz PUBLIC_IP 80.
Programs requiring inbound UDP (voice servers, some game servers and WireGuard servers) are unsupported.