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

Connect servers privately with WireGuard and site-to-site VPN

Inspect your environment fabric in the 3D Network Builder, save network checkpoints and connect private subnets over WireGuard VPN.

Intermediate
22 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 WireGuard 1.0, Ubuntu 24.04, sau CLI 0.2.0.

What you will have at the end

Your Servers Are Up virtual machines, workstation devices, and remote office or cloud sites will communicate over an authenticated, modern ChaCha20-Poly1305 WireGuard mesh and private VPC subnet fabric—visualized across four layers (L1 WAN/VPN peers, L2 Gateway/Firewall, L3 Subnets/VLANs, and L4 Compute Nodes) on /dashboard/network—with saved rollback checkpoints before every topology change.

Before you start

  • At least one running server on Compute > Servers (/dashboard/instances) or an active environment on Billing & account > Plan & capacity (/dashboard/environment).
  • The official WireGuard client installed on your laptop (macOS, Windows, or Linux) or wireguard-tools (wg, wg-quick) on a remote Linux gateway if you are establishing a site-to-site tunnel.
  • Optional: sau CLI v0.2.0 (sau network ...) for scripting checkpoints and tunnel audits.

Steps

1. Inspect your tenant-isolated network map and save a checkpoint

Open Network > Map (/dashboard/network?tab=map). The four-plane fabric view shows only your own tenant's WAN edge, perimeter rules, private RFC1918/RFC6598 subnets, and compute nodes.

Before adding subnets, VPN peers, or east-west ACL changes, save a named configuration checkpoint so you can roll back with one click or command:

sau network checkpoint-create pre-vpn-rollout --description "Baseline fabric before adding workstation and branch VPN peers"
sau network checkpoints-list -o table

2. Connect your workstation with per-server or environment WireGuard VPN

To reach PostgreSQL, Redis, SSH, or internal admin dashboards without opening any public ports:

  1. Open Network > VPN (/dashboard/network?tab=vpn) (or open a single server's VPN panel if you only need point-to-point access to one VM).
  2. Click Add VPN peer / device, name it (for example ops-macbook), and download or scan the generated .conf profile. Keys are generated for your device alone; only the public key is registered on the gateway.
  3. Import the profile into your local WireGuard app—or save it on Linux as /etc/wireguard/sau-dev.conf with 0600 permissions:
[Interface]
PrivateKey = YOUR_LOCAL_DEVICE_PRIVATE_KEY
Address = 172.30.1.50/32, fd10:1::50/128
DNS = 172.30.1.1

[Peer]
PublicKey = SAU_ENVIRONMENT_VPN_PUBLIC_KEY
AllowedIPs = 172.30.1.0/24, fd10:1::/64
Endpoint = 203.0.113.10:51820
PersistentKeepalive = 25

Notice AllowedIPs = 172.30.1.0/24, fd10:1::/64 (split-tunnel mode): only traffic bound for your private cloud subnet enters the encrypted tunnel, while normal internet browsing stays on your local connection.

3. Build a site-to-site tunnel to an office router or remote cloud VPC

To bridge an entire remote subnet (for example an OpenStack or branch subnet 172.24.10.0/24) with your Servers Are Up environment subnet (172.30.1.0/24):

  1. On Network > VPN (/dashboard/network?tab=vpn), choose Site-to-site tunnel, enter the remote gateway's public IPv4 (198.51.100.88:51820), paste its WireGuard public key, and declare the routed remote CIDR (172.24.10.0/24).
  2. On the remote Linux gateway (198.51.100.88), enable kernel IPv4/IPv6 forwarding and bring up the matching WireGuard interface:
sudo tee /etc/sysctl.d/99-sau-vpn-forward.conf > /dev/null <<'EOF'
net.ipv4.ip_forward = 1
net.ipv6.conf.all.forwarding = 1
EOF
sudo sysctl --system

sudo tee /etc/wireguard/wg-s2s0.conf > /dev/null <<'EOF'
[Interface]
PrivateKey = REMOTE_SITE_GATEWAY_PRIVATE_KEY
Address = 172.30.255.2/30
ListenPort = 51820

[Peer]
PublicKey = SAU_ENVIRONMENT_GATEWAY_PUBLIC_KEY
Endpoint = 203.0.113.10:51820
AllowedIPs = 172.30.1.0/24, 172.30.255.1/32
PersistentKeepalive = 25
EOF
sudo chmod 0600 /etc/wireguard/wg-s2s0.conf
sudo systemctl enable --now wg-quick@wg-s2s0
  1. Add a static route on hosts inside 172.24.10.0/24 (or on your branch router's DHCP gateway) pointing 172.30.1.0/24 to the Linux WireGuard gateway.

4. Segment east-west database tiers with private subnets

On Network > Map (/dashboard/network?tab=map), Layer 3 lets you separate public-facing ingress nodes from isolated database and storage VLANs so a compromised web container cannot scan unrelated internal workloads. Bind internal services (such as PostgreSQL listen_addresses = '172.30.1.27') strictly to the server's private interface.

Check that it works

Bring up your tunnel, inspect the cryptographic handshake and transfer counters, and verify private reachability:

sudo wg show
sau network tunnels-list -o table
ping -c 3 172.30.1.27

sudo wg show prints a latest handshake timestamp within the last two minutes and non-zero transfer: ... received, ... sent counters. On Network > Map (/dashboard/network?tab=map), your peer badge updates from never connected to active.

What can go wrong

  • Tunnel activates locally (wg-quick up succeeds) but latest handshake never appears. WireGuard is connectionless UDP (51820/udp by default) and wg-quick up succeeds even if packets drop upstream. Confirm UDP 51820 is not blocked by guest/corporate Wi-Fi and verify both sides switched PublicKey values accurately (a common mistake is pasting a peer's own public key into [Peer]).
  • Large HTTPS or SQL responses stall over the VPN while small ping packets succeed. Classic Path MTU blackhole! Add MTU = 1380 under [Interface] on both peers (especially over PPPoE fiber or cloud VXLAN underlays) and restart wg-quick.
  • A routing or firewall edit broke internal connectivity. Restore your saved checkpoint immediately: sau network checkpoint-restore pre-vpn-rollout or click Restore on Network > History (/dashboard/network?tab=history).

Good practice

  • Issue one unique WireGuard peer key pair per engineer device and per remote site—never share a single .conf across teammates, because revoking one lost laptop should take one click without disrupting anyone else.
  • Save a named checkpoint (sau network checkpoint-create ...) before every firewall or subnet refactor.
  • Combine private networking with Access > Identity governance & ZTNA (/dashboard/entra-suite) and Access > Cloud bastion (/dashboard/bastion) when contractors need application-specific access rather than L3 subnet routing.

Where to go next

  • Open only the ports your application needs
  • Integrate DigitalOcean, AWS and custom clouds into your environment
  • Configure OIDC 1.0, SCIM 2.0, ZTNA and Cloud Bastion

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 Connect servers privately with WireGuard and site-to-site VPN documentation guide cover?
Inspect your environment fabric in the 3D Network Builder, save network checkpoints and connect private subnets over WireGuard VPN. It is rated intermediate difficulty (22 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 Connect servers privately with WireGuard and site-to-site VPN?

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. Inspect your tenant-isolated network map and save a checkpoint2. Connect your workstation with per-server or environment WireGuard VPN3. Build a site-to-site tunnel to an office router or remote cloud VPC4. Segment east-west database tiers with private subnetsCheck that it worksWhat can go wrongGood practiceWhere to go next