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

Put your own domain on an application and enable HTTPS

Configure DNS A, AAAA and CNAME records in Cloud DNS or an external registrar and automate TLS certificate issuance and renewal.

Beginner
15 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 SAU Cloud DNS, Caddy 2.8, Let's Encrypt ACME v2, sau CLI 0.2.0.

What you will have at the end

Your custom apex domain (example.com) and subdomains (app.example.com, api.example.com) will resolve through authoritative DNS with optional DNSSEC signing, route traffic to your Servers Are Up Linux VPS, container stack, or Network > API gateway & edge WAF (/dashboard/api-gateway), and renew TLS 1.3 HTTPS certificates automatically at least 30 days before expiration.

Before you start

  • A registered domain name at any domain registrar (such as Cloudflare Registrar, Porkbun, Namecheap, or Route 53).
  • A running application or server on Servers Are Up with a public IPv4 address (for example 203.0.113.25 on Compute > Servers at /dashboard/instances) or an Edge Gateway hostname on Network > API gateway & edge WAF (/dashboard/api-gateway).
  • dig or nslookup and curl on your workstation to verify propagation and TLS handshakes.

Steps

1. Create a public zone in Cloud DNS (or open your external DNS panel)

You can host authoritative DNS directly inside Network > Cloud DNS zones (/dashboard/cloud-dns)—with one-click DNSSEC signing and BIND zone export—or keep your existing DNS provider:

# Create an authoritative public zone with DNSSEC via the sau CLI
sau network dns-create example.com --dnssec

# Inspect your zone and assigned nameservers
sau network dns-list --zone example.com -o table

If you host the zone in Network > Cloud DNS zones (/dashboard/cloud-dns), update your domain registrar's nameserver (NS) delegation to match the authoritative nameservers displayed in the zone header. If you keep your registrar's DNS, simply add the records in Step 2 there.

2. Add A, CNAME, and CAA DNS records

Create explicit records with a short 300-second TTL during initial cutover so typos can be corrected in five minutes:

Name Type Value TTL Purpose
@ A 203.0.113.25 300 Routes apex example.com to your server's public IPv4
www CNAME example.com. 300 Aliases www.example.com to the apex
app A 203.0.113.25 300 Routes app.example.com to your web server
@ CAA 0 issue "letsencrypt.org" 3600 Restricts certificate issuance to Let's Encrypt

Verify DNS resolution against a public recursive resolver (1.1.1.1 or 8.8.8.8) before starting ACME certificate issuance so you do not trigger Let's Encrypt validation rate limits:

dig @1.1.1.1 +short A app.example.com
dig @1.1.1.1 +short CAA example.com

3. Open ports 80 and 443 in your perimeter firewall

Let's Encrypt's standard HTTP-01 challenge connects to TCP port 80 (/.well-known/acme-challenge/...), and TLS-ALPN-01 plus HTTPS visitors connect to TCP/UDP port 443.

Open Network > Firewall (/dashboard/network?tab=firewall) and confirm both 80/tcp and 443/tcp (plus 443/udp for HTTP/3 QUIC) are permitted inbound to your server. Keep your backend application port (3000, 8080, or 5432) bound to 127.0.0.1 so all external requests pass through TLS termination.

4. Terminate HTTPS and redirect www to canonical apex

On a Linux VPS running Caddy, add both your apex redirect and your app proxy to /etc/caddy/Caddyfile and reload:

sudo tee /etc/caddy/Caddyfile > /dev/null <<'EOF'
www.example.com {
    redir https://example.com{uri} permanent
}

example.com, app.example.com {
    encode zstd gzip
    header Strict-Transport-Security "max-age=31536000; includeSubDomains"
    reverse_proxy 127.0.0.1:3000
}
EOF

sudo caddy validate --config /etc/caddy/Caddyfile
sudo systemctl reload caddy

If you prefer managed layer-7 rate limiting, subscription API keys, and OWASP WAF rules in front of your origin without managing reverse proxies on the VM, attach your domain on Network > API gateway & edge WAF (/dashboard/api-gateway) instead; see Route APIs with Edge WAF, rate limits and Cloud DNS.

Check that it works

Inspect the live X.509 certificate chain, issuer, SANs, and HTTP-to-HTTPS redirect from your terminal:

curl -fsSI http://app.example.com | grep -iE "^HTTP/|^location:"
echo | openssl s_client -servername app.example.com -connect app.example.com:443 2>/dev/null \
  | openssl x509 -noout -subject -issuer -dates

http://app.example.com returns 308 Permanent Redirect to https://app.example.com/, and openssl x509 prints issuer=C = US, O = Let's Encrypt with a valid notAfter timestamp ~90 days out.

What can go wrong

  • Certificate issuance fails because an old CAA record authorizes a different CA. Run dig +short CAA example.com. If CAA records exist and do not include letsencrypt.org, Let's Encrypt is required by RFC 8659 to refuse issuance until you add 0 issue "letsencrypt.org".
  • Redirect loop (ERR_TOO_MANY_REDIRECTS) when using an external proxy CDN. If you place an external CDN in front of Caddy in "Flexible SSL" mode, the CDN talks to Caddy over plain HTTP 80, causing Caddy to redirect back to HTTPS endlessly. Always set upstream TLS mode to Full (Strict) so end-to-end traffic is encrypted on 443.
  • Internal services resolve public IPs instead of private VPC addresses. Create a split-horizon PRIVATE_VNET zone (sau network dns-create internal.example --private) in Network > Cloud DNS zones (/dashboard/cloud-dns) for east-west service discovery.

Good practice

  • Raise your DNS TTL from 300 seconds to 3600 seconds once cutover is verified so resolvers cache answers and absorb transient DNS blips.
  • Monitor external HTTPS expiration and response latency from Automation > Operator toolbox (/dashboard/saas) or your uptime monitor so a blocked port 80 never silently breaks renewal at day 60.
  • Export a backup BIND zone file from Network > Cloud DNS zones (/dashboard/cloud-dns) into version control after major DNS changes.

Where to go next

  • Route APIs with Edge WAF, rate limits and Cloud DNS
  • Open only the ports your application needs
  • Deploy a Next.js application on a Servers Are Up Linux server

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 Put your own domain on an application and enable HTTPS documentation guide cover?
Configure DNS A, AAAA and CNAME records in Cloud DNS or an external registrar and automate TLS certificate issuance and renewal. It is rated beginner difficulty (15 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 Put your own domain on an application and enable HTTPS?

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. Create a public zone in Cloud DNS (or open your external DNS panel)2. Add A, CNAME, and CAA DNS records3. Open ports 80 and 443 in your perimeter firewall4. Terminate HTTPS and redirect www to canonical apexCheck that it worksWhat can go wrongGood practiceWhere to go next