Skip to main content
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog
Servers Are Up
Virtual Datacenter
PricingFree Tools
Sign inBrowse catalog

Loading…

Servers Are Up

Your apps, automation and data on hardware we own. Build a private stack with predictable capacity and access through your dashboard, API or SSH.

SLA with service creditsOwned hardwareUS-based

Make room for your next idea

Explore the capacity, apps and access options that fit your workload. Check current availability and your total before you buy.

Sign up freeView Pricing

Products

  • Linux VPS
  • Windows VPS
  • Cloud & SaaS Services
  • Cloud Storage (Azure)
  • Virtual Datacenter
  • AI & Agent Hosting
  • Containers
  • Instant Apps
  • Software Platforms
  • Network builder
  • Game Servers
  • Pricing

Resources

  • Free Network Tools
  • 2026 Pricing Benchmark
  • Live SVG Badges
  • Latency & Speed Test
  • Guides & Tutorials
  • Documentation
  • API Reference
  • MCP Server
  • CLI & SDKs
  • OpenAPI & llms.txt
  • Use Cases
  • Free Migration
  • Uptime & Reliability
  • Datacenter
  • System Status
  • Network
  • Provider Comparisons Hub
  • Compare Providers

Company

  • About Us
  • Enterprise
  • Security Architecture
  • Trust Center
  • Blog
  • FAQ
  • Compliance
  • Startup Program
  • Open-Source Sponsorship
  • Press & Media Kit
  • Referral Program
  • Help Center
  • Contact Us
© Servers Are Up
TermsPrivacySLARefund PolicyDPAAcceptable Use
Service information
Docs
  • Documentation Hub
  • Choose a Product
    VMs, Containers & Cloud
  • First Linux Server
    SSH, Firewall & Apps
  • Windows Server 2025
    BYOL & Remote Desktop
  • Remote Access
  • Troubleshooting
  • FAQ
  • All Product Guides
    29 Step-by-Step Guides
  • Cloud & SaaS Catalog
    112 Cloud & SaaS Offerings
  • Azure Cloud Storage
    Hot/Cool/Archive & WORM
  • Resource Manager & RBAC
    Groups, Tags & Locks
  • Multi-Model Cloud DB
    JSONB, SQL & pgvector
  • Cloud Identity & ZTNA
    OIDC, SCIM & PIM
  • Key Vault & KMS
    Secrets & Envelope Keys
  • Cloud SIEM, SOAR & DLP
    Posture & Threat Response
  • API Gateway & Cloud DNS
    Edge WAF & DNS Zones
  • Serverless, Workflows & IoT
    Functions, Queues & DAGs
  • SaaS, Governance & Vault
    Budgets & Off-Host GRS
  • Build Web Apps with AI
  • Next.js and React
  • TypeScript and Node.js
  • npm and Tooling
  • Data and APIs
  • Deploy and Operate
  • Tutorials
  • Infrastructure
  • Automation & Regions
  • API Overview
  • API v1 Reference
    Endpoints & 23 Scopes
  • MCP Server
    129 AI Agent Tools
  • Swagger / OpenAPI 3.1
  • API Playground
  • Versioning & Sunset
  • API Token Security
    Authentication & Tokens
  • Instances API
    Compute Resources
  • Networking API
    Networks & Ports
  • Storage API Availability
    Volumes & Backups
  • Webhooks & Events
    Event Notifications
  • Rate Limits & Best Practices
    Throttling & Retries
  • sau CLI Reference
    34 Commands (v0.2)
  • Browser Web CLI
  • SDKs
  • Infrastructure as Code
    Terraform & Ansible
  • Code Examples
  • CLI & SDK Guides
  • Security Guides
  • Security at a Glance
  • Zero Trust Architecture
  • Live Trust Center
  • Compliance
Need help?

Loading documentation...

Documentation/products

Open only the ports your application needs

Configure default-deny perimeter firewall rules, CIDR source allow-lists and TCP or UDP port forwards for servers on Servers Are Up.

Beginner
14 min
Updated 2026-11-12

Deploy Ready-to-Run Infrastructure in Seconds

Linux VMs from $6/mo · Pooled Virtual Datacenters from $12/mo · Use code WELCOME20 for 20% off your first order.

Browse ServersView Pricing

Commands checked on 2026-11-12 with Servers Are Up Network Fabric, Ubuntu 24.04 nftables/ufw, sau CLI 0.2.0.

What you will have at the end

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.

Before you start

  • A running Linux, Windows, Docker, or Game server on Compute > Servers (/dashboard/instances).
  • A short list of the exact ports and protocols (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.
  • Your workstation or upstream CDN's public IPv4 CIDR (for example 198.51.100.42/32) if you are opening an administrative port.

Steps

1. Audit your current perimeter exposure

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

2. Add a port forward or perimeter allow rule with a source CIDR

Open Network > Public access (/dashboard/network?tab=ingress) or Network > Firewall (/dashboard/network?tab=firewall) and create only the rules your workload requires:

  • Public Web HTTPS: Protocol TCP (and UDP for HTTP/3), port 443, Source CIDR 0.0.0.0/0, target server prod-web-01.
  • Restricted Admin / Webhook Ingress: Protocol 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"
  }'

3. Align the guest OS firewall inside your VM

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

4. Toggle rules off instead of deleting them during maintenance

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.

Check that it works

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.

What can go wrong

  • Opening a port in /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.
  • Connections hang and time out (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.
  • Game server players cannot join even though TCP is open. Most multiplayer games (Palworld, Rust, FiveM, Valheim, CS2) use UDP for gameplay traffic. Confirm the rule allows UDP on the game port; see Launch your first multiplayer game server and customize settings.

Good practice

  • Never expose database ports (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.
  • Place public HTTP APIs behind Network > API gateway & edge WAF (/dashboard/api-gateway) to add per-IP rate limiting and SQLi/XSS WAF inspection before traffic reaches your server.
  • Review Network > History (/dashboard/network?tab=history) weekly to audit every port change across your team.

Where to go next

  • Connect servers privately with WireGuard and site-to-site VPN
  • Route APIs with Edge WAF, rate limits and Cloud DNS
  • Hunt threats with KQL, automate SOAR and enforce DLP

Related Articles

Create a scoped API key and send your first v1 request

Read more

Route APIs with Edge WAF, rate limits and Cloud DNS

Read more

Purchase Azure-backed cloud storage with WORM locks and SAS

Read more

Frequently Asked Questions

What does the Open only the ports your application needs documentation guide cover?
Configure default-deny perimeter firewall rules, CIDR source allow-lists and TCP or UDP port forwards for servers on Servers Are Up. It is rated beginner difficulty (14 min) and applies to Servers Are Up infrastructure and workflows.
Can I manage or automate these steps through the Servers Are Up dashboard, REST API v1, or MCP server?
Yes. Every Servers Are Up server includes browser-based SSH, WebRDP, and VNC console access in the dashboard, plus programmatic control via the REST API v1 (/api/v1) and hosted Model Context Protocol server (/api/mcp/v1) using a scoped Personal Access Token.

Need hands-on help with Open only the ports your application needs?

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.

Was this article helpful?

On this page

What you will have at the endBefore you startSteps1. Audit your current perimeter exposure2. Add a port forward or perimeter allow rule with a source CIDR3. Align the guest OS firewall inside your VM4. Toggle rules off instead of deleting them during maintenanceCheck that it worksWhat can go wrongGood practiceWhere to go next