Deploy App
Domains and HTTPS
Point a domain at your app, add more domains, and turn on free HTTPS with Apply SSL.
Point the domain at the server
At your domain registrar or DNS provider, add an A record for each domain pointing at the server's public IP address. The app's Domains tab lists the exact records to create.
| Type | Name | Value |
|---|---|---|
| A | example.com (often written @) | 203.0.113.7 |
| A | www.example.com (often written www) | 203.0.113.7 |
DNS changes usually show up within minutes, sometimes up to an hour.
Turn on HTTPS — Apply SSL
HTTPS is never switched on silently: press Apply SSL on the Domains tab when the DNS is ready. We then:
- Check each domain's DNS points at this server. Domains that don't are skipped and listed, so one forgotten record doesn't block the rest.
- Get a free certificate from Let's Encrypt for all the ready domains.
- Switch them to HTTPS and send HTTP visitors to HTTPS.
The certificate renews by itself every two to three months. The Domains tab shows when it expires, and an uptime monitor warns you if renewal ever fails.
Behind Cloudflare or another proxy? Their DNS shows the proxy's address, not your server's. Tick Behind a proxy/CDN — skip the DNS check before pressing Apply SSL.
It failed? Almost always one of: the A record doesn't point here yet, or a firewall (security group) blocks port 80. Let's Encrypt has to reach the server on port 80 to prove you own the domain. Fix it and press Apply SSL again.
More domains
Add another domain on the Domains tab at any time — www.example.com, a second
brand, an old domain. It's served right away over HTTP; press Apply SSL
again to add it to the certificate. Extra domains can be removed again.
The main domain can't be changed or removed. It names the app's folder, nginx site and container on the server. To move an app to a new main domain, create a new app with that domain and delete the old one.
One domain belongs to one app: you can't add a domain another app already uses.