Loading…
Loading documentation...
Configure default-deny perimeter firewall rules, CIDR source allow-lists and TCP or UDP port forwards for servers on Servers Are Up.
Commands checked on 2026-11-12 with Servers Are Up Network Fabric, Ubuntu 24.04 nftables/ufw, sau CLI 0.2.0.
Your server will operate under two independent layers of least-privilege network defense: the Servers Are Up datacenter perimeter firewall and NAT gateway (which drops unwanted internet traffic before it ever reaches your VM's virtual NIC) plus a clean host-level firewall inside your guest OS, exposing only the exact TCP or UDP ports and source IP CIDRs your application serves.
/dashboard/instances).tcp vs udp) your application listens on—for example 80/tcp and 443/tcp+udp for a web app, or 8211/udp for a Palworld server.198.51.100.42/32) if you are opening an administrative port.Every Servers Are Up environment enforces default-deny inbound at the network edge. Inspect your active perimeter firewall rules and port forwards from Network > Firewall (/dashboard/network?tab=firewall), Network > Public access (/dashboard/network?tab=ingress), or the sau CLI:
sau network firewall-list -o table
curl -fsSL "https://serversareup.com/api/v1/instances/YOUR_INSTANCE_ID/port-forwards" \
-H "Authorization: Bearer sau_your_token_here" | jq .
Save a network checkpoint before modifying production rules:
sau network checkpoint-create before-port-changes
Open Network > Public access (/dashboard/network?tab=ingress) or Network > Firewall (/dashboard/network?tab=firewall) and create only the rules your workload requires:
TCP (and UDP for HTTP/3), port 443, Source CIDR 0.0.0.0/0, target server prod-web-01.TCP, Source CIDR restricted to your office static IP (198.51.100.42/32) or webhook sender range—never 0.0.0.0/0 for SSH (22), RDP (3389), PostgreSQL (5432), Redis (6379), Docker API (2375), or Kubernetes (6443).You can also create an instance-scoped port forward programmatically via POST /api/v1/instances/{id}/port-forwards (which reserves a durable provider command and responds with 202 Accepted):
curl -fsSL -X POST "https://serversareup.com/api/v1/instances/YOUR_INSTANCE_ID/port-forwards" \
-H "Authorization: Bearer sau_your_token_here" \
-H "Content-Type: application/json" \
-d '{
"protocol": "tcp",
"publicPort": 443,
"privatePort": 443,
"sourceCidr": "0.0.0.0/0",
"description": "Production HTTPS ingress"
}'
Defense in depth means keeping a local firewall enabled inside Ubuntu (ufw or nftables) or Windows (New-NetFirewallRule) so east-west peers on the same private subnet can also reach only intended ports.
Connect through the browser console (/dashboard/console)—so you cannot lock yourself out—and configure ufw on Ubuntu 24.04:
sudo ufw default deny incoming
sudo ufw default allow outgoing
sudo ufw allow 80/tcp comment 'ACME HTTP and redirect'
sudo ufw allow 443/tcp comment 'HTTPS TLS 1.3'
sudo ufw allow 443/udp comment 'HTTP/3 QUIC'
# Allow PostgreSQL only from your private VPC subnet, never from public interfaces
sudo ufw allow from 172.30.1.0/24 to any port 5432 proto tcp comment 'VPC Postgres'
sudo ufw --force enable
sudo ufw status numbered
On Network > Map (/dashboard/network?tab=map), Layer 2 shows every "Way in from the internet" card with a live green/off indicator. When you only need temporary SSH or migration ingress for an hour, toggle that port forward off as soon as maintenance ends—nothing on the internet can reach it while disabled, and you preserve the port mapping for next time.
Verify from inside the server which sockets are bound, then test from an external machine that allowed ports respond while closed ports drop cleanly:
# Inside the Linux server: inspect listening TCP/UDP sockets
sudo ss -tulnp
# From an external workstation: 443 succeeds, 5432 times out at the edge
nc -zv -w 3 203.0.113.25 443
nc -zv -w 3 203.0.113.25 5432 || echo "Port 5432 is safely blocked at the perimeter"
Run a Cloud Security Posture scan (sau security scan) or open Operations > Security posture & DLP (/dashboard/defender-purview) to confirm zero exposed administrative or database ports lower your Secure Score.
/dashboard/network succeeds, but connections still return Connection refused. A Connection refused (TCP RST) means the packet passed the perimeter firewall and reached your VM, where nothing is listening on that port (or your app is bound to 127.0.0.1 instead of 0.0.0.0). Check sudo ss -tulnp inside the server.Operation timed out). Packets are being dropped either at Network > Firewall (/dashboard/network?tab=firewall), by a mismatched sourceCidr, or by ufw/nftables inside the guest OS.UDP on the game port; see Launch your first multiplayer game server and customize settings.3306, 5432, 6379, 27017, 9200) to 0.0.0.0/0, even "just for five minutes" during setup—automated scanners index and brute-force open database ports continuously./dashboard/api-gateway) to add per-IP rate limiting and SQLi/XSS WAF inspection before traffic reaches your server./dashboard/network?tab=history) weekly to audit every port change across your team.Every Servers Are Up virtual machine and container includes an integrated HTML5 browser-based SSH, RDP, and VNC console in your dashboard, default-off inbound firewall rules with per-IP allow-lists, and full programmatic control via REST API v1 and Model Context Protocol (MCP). Explore our Virtual Datacenter Plans or reach out to Servers Are Up Support.