Add a domain

Give a hostname to your app, and serve it over HTTPS.

Most apps get a generated deplo.site address when they are created. This page puts your own hostname in front of one.

Point the domain at the server

Domain on Cloudflare?

Connect its zone once under Settings -> General -> Automatic DNS and Deplo creates the record for you: skip this part. See Automatic DNS.

Find the server's public IP

It is the hex part of the app's generated URL (cb00710a is 203.0.113.10), and it is on the server's card in Settings -> Servers.

Create an A record

At your DNS provider, point an A record for the hostname at the server, for example app.example.com -> 203.0.113.10.

If the server has IPv6, add an AAAA record too. Once the domain is added, its row prints the address, for example 2001:db8::10.

No AAAA unless the server has IPv6

An AAAA record that points anywhere but this server makes the domain misconfigured, even next to a correct A record. If the row prints no IPv6 address, create only the A record.

Add it in Deplo

Open the app's Domains tab

Click Add Domain and type the hostname, for example app.example.com.

The Domains tab of an app

Turn on HTTPS

Under HTTPS, set Certificate to Let's Encrypt. It starts on None (no certificate), which serves plain HTTP.

Behind Cloudflare's proxy, Deplo follows Cloudflare's SSL mode by itself: Let's Encrypt under Full or Full (strict), no certificate under Flexible.

The Add a domain dialog with the DNS check

Confirm, and wait for DNS

Click Add domain. Deplo checks the DNS right away and keeps checking until it points here.

Set it as primary

Click the star on the domain's row to make it the app's main address. The star stays disabled while the domain is misconfigured.

Let's Encrypt validates over HTTP: port 80 must be reachable even for a site served on 443.

No domain yet?

The Add Domain dialog has a Generate button that fills in a new deplo.site hostname.

Deplo creates no generated address when it cannot tell where traffic should land:

  • a compose app where no service declares ports: or expose:, such as a stack of workers
  • an app from a database image, like redis or postgres, or an image that declares no port

Nothing is broken: the app has no front door yet. Open Add Domain, click Generate, and on a compose app pick the container it routes to.

Troubleshooting

SymptomWhat to check
Stuck on Waiting for DNSThe record has not propagated, or points at another machine. Check with dig +short app.example.com.
misconfigured with a correct A recordAn AAAA record points elsewhere. Check with dig +short AAAA app.example.com, then remove it or point it at the server.
The browser shows a certificate warningThe certificate is still None, has not issued yet, port 80 is closed, or the domain resolves elsewhere. A browser can also hold an old certificate in cache.
404 from the proxyDNS and certificate are fine but no route matches. Usually the app is stopped, or runs on a different server.

More in Domains and TLS.

Next steps

Did this page help you?

On this page