Connect a custom domain
Connect a custom domain to your Servor status page with a CNAME — and fix the Cloudflare orange-cloud proxy issue that blocks the certificate.
By default your status page lives at a Servor address like
acme.status.servor.app. Connecting a custom domain lets you serve it at
your own address instead — for example status.acme.com — which looks more
professional and keeps your brand front and center.
This guide walks you through pointing a domain at Servor with a CNAME record, and covers the single most common problem: the Cloudflare orange-cloud proxy, which must be turned off or the certificate won't issue.
Before you start
- You need a status page already created.
- You need access to your domain's DNS settings (at your registrar or DNS provider — Cloudflare, GoDaddy, OVH, Route 53, etc.).
- Custom domains are limited by plan — check plans and limits if you don't see the option.
Connect the domain
Add the domain in Servor
Open your status page settings from
Status pages in Servor, go to
Custom domain, and enter the domain
you want to use (for example status.acme.com). Servor shows you the CNAME
target to point at.
Create a CNAME record
In your DNS provider, add a CNAME record for your subdomain
(status) pointing to the target Servor gave you. Save it.
Turn off any proxy (Cloudflare users, read this)
If your DNS is on Cloudflare, set the record to DNS only — the grey cloud, not the orange one. See the Cloudflare orange-cloud gotcha warning below.
Wait for verification and the certificate
Back in Servor, wait for the domain to verify and the TLS certificate to issue. This is usually quick but DNS changes can take a while to propagate. The page shows a live certificate status so you know exactly where things stand.
The Cloudflare orange-cloud gotcha
If your domain is on Cloudflare, the CNAME record must be set to DNS only (grey cloud), not Proxied (orange cloud). When the orange cloud is on, Cloudflare intercepts the traffic and terminates TLS itself, which stops Servor from issuing a certificate and serving your page — you'll see the certificate stay stuck or the page fail to load. Click the orange cloud next to your record so it turns grey, save, and the certificate will issue.
How serving works
Your status page is served through Vercel, which provisions and renews the TLS certificate automatically once the domain is verified. That's why the record has to resolve straight to the target: any proxy in front of it (like Cloudflare's orange cloud) prevents the certificate from being issued. Once it's issued, HTTPS is handled for you — there's nothing to renew by hand.
Certificate status
The custom domain screen shows a live certificate status so you don't have to guess:
| Status | What it means |
|---|---|
| Pending | The domain is verifying or the certificate is being issued — wait. |
| Active | The certificate is live and your page is served securely over HTTPS. |
| Error | Something is blocking issuance — most often a proxy (orange cloud) or a wrong/missing CNAME. |
Troubleshooting
- Certificate stuck on "pending" for a long time — check the CNAME points to the exact target Servor gave you, and that no proxy (Cloudflare orange cloud) is in front of it.
- "Error" status — re-check the record's target for typos, and confirm it's set to DNS only. Remove any conflicting A or AAAA record on the same host.
- Page loads on the Servor URL but not the custom one — DNS may still be propagating; give it time, then re-verify.
- Still stuck? See Troubleshooting.