Configure

Domains & HTTPS

Every app gets an HTTPS address on deploy. You can also put it on your own domain — the certificate is issued and renewed for you.

Your automatic address#

format
https://<service-name>-<id>.cloud.crowtherlabs.com
  • <service-name> is the service's name, lower-cased with spaces and symbols turned into hyphens — "Customer Portal" becomes customer-portal.
  • <id> is six characters fixed when the service is created, so two services with the same name never clash. The address stays the same across deploys.
  • HTTPS works from the first request; plain HTTP is redirected to HTTPS.
  • Find it at the end of the deploy log and on the service's Domains tab.

Renaming a service changes its address

The name part follows the service's current name, so after a rename the next deploy moves the app to a new address and the old one stops working. Anything that calls the old address — a frontend, a webhook, a mobile app — needs updating. Put stable integrations on a custom domain, which never changes.

Using your own domain#

  1. Deploy the service first

    The domain has to point at the server the app runs on, so the app must be running.

  2. Add the domain

    Open the service's Domains tab, enter the domain (for example api.example.com) and click Add domain.

  3. Create the DNS record it shows you

    At your DNS provider (Cloudflare, Namecheap, GoDaddy, Route 53…):

    Your domainRecord typePoints to
    A subdomain — api.example.com, app.example.comCNAMEyour platform address, e.g. orders-api-a1b2c3.cloud.crowtherlabs.com
    A root domain — example.comAthe server IP shown on the Domains tab

    Prefer the CNAME whenever you can: if the app ever moves to another server, a CNAME keeps working and an A record would need updating (the Domains tab shows the new IP if that happens).

  4. Wait for Active

    The Domains tab re-checks every 20 seconds and moves through the statuses below. Once DNS is correct, the certificate usually arrives in under a minute. Check now checks immediately.

Your automatic address keeps working alongside the custom domain. Adding, changing or removing a domain never restarts the app.

What the statuses mean#

StatusMeaningWhat to do
Waiting for a deployThe service isn't running anywhere.Deploy it.
Waiting for DNSThe domain doesn't point at the app's server yet.Create or fix the record; DNS changes can take a few minutes to spread.
DNS needs fixingThe domain points here and somewhere else too.Remove extra A records and any AAAA record for the name.
Issuing certificateDNS is right; the certificate is being issued.Nothing — usually under a minute.
ActiveServed over HTTPS with a valid certificate.Done. Renewal is automatic.

DNS mistakes that stop the certificate#

Cloudflare: set the record to "DNS only"

With the orange cloud (Proxied) on, the domain resolves to Cloudflare's servers instead of ours, so the certificate can't be issued and the status stays at Waiting for DNS. Click the cloud so it turns grey — DNS only.

Remove AAAA (IPv6) records

Apps are served over IPv4 only. The certificate authority tries IPv6 first, so a leftover AAAA record — often from the previous host — sends the check to the wrong server.

Delete the old records

When moving an existing site here, delete its old A/CNAME records for that name rather than adding a second one next to them.

Lower the TTL before a move

For a live site, set the record's TTL to 60–300 seconds a day before switching, so visitors follow the change within minutes instead of hours.

Rules for custom domains#

  • One domain per service, and a domain can be attached to only one service.
  • Each hostname separately: example.com and www.example.com are two domains. Wildcards (*.example.com) aren't supported.
  • Addresses under cloud.crowtherlabs.com and the platform's own address can't be added.
  • Update your app's own settings for the new name — allowed origins (CORS), cookie domains, OAuth redirect URLs, Django's ALLOWED_HOSTS.

About the certificates#

  • Issued by Let's Encrypt, trusted by every browser and phone.
  • Valid for 90 days and renewed automatically about a month before expiry. Nothing to do.
  • Your app receives plain HTTP from the platform's router, with X-Forwarded-Proto: https — see Behind the router.