Why isn't my custom domain working yet?
Troubleshoot DNS verification, SSL provisioning, assignment, and routing for a custom domain.
Use this article when a custom domain does not verify, does not load, shows a certificate warning, or redirects unexpectedly.
Custom domains go through several steps: DNS verification, assignment to a deployment, SSL certificate provisioning, and routing. A problem at any step can make the domain look broken even when earlier steps succeeded.
Verification is still pending
If the domain shows "Custom domain - verification pending", Clipido has not confirmed your TXT record yet.
Check these points:
- The TXT record name is exactly
_clipido-verification.{your-full-domain}(for example_clipido-verification.media.yoursite.com). - The TXT value matches the token shown in "Show setup instructions" with no extra spaces.
- You waited at least "5 to 15 minutes" after adding the record. click Verify domain again from the domain menu.
If verification still fails, the toast reads "DNS verification failed. Please ensure you've added the TXT record. DNS propagation can take 5-15 minutes."
The domain is verified but not assigned
A verified domain does not serve your workspace until it is assigned to a deployment.
- Open Admin Center → "Deployments" → your deployment → "Branding".
- Confirm Domain is set to your custom domain, not
{slug}.{clipido-domain} (Default).
If you try to assign an unverified domain, Clipido returns "Domain must be verified before it can be assigned."
DNS routing is wrong
Even after verification, visitors need a CNAME record pointing your subdomain to Clipido's CNAME target (shown in "Show setup instructions", for example domain.clipido.link in production).
Common mistakes:
| Problem | What to check |
|---|---|
| Missing CNAME | Add the CNAME record from the setup instructions |
| Wrong CNAME target | Copy the target exactly from Admin Center; it differs by environment |
| Wrong CNAME name | Use the subdomain label shown (for example media, not the full domain) |
| Cloudflare proxy enabled | Set the record to DNS only (grey cloud), not proxied, if your provider is Cloudflare |
If the hostname is not registered in Clipido at all, visitors see "Domain Not Found" with "This domain is not configured."
SSL certificate is still provisioning
In production, Clipido provisions a Let's Encrypt certificate after you assign a verified domain. Until the certificate status is "ready", you may see a browser certificate warning or incomplete redirects from the default subdomain.
Certificate provisioning can take several minutes after assignment. If it stays in a failed state, confirm the CNAME points to Clipido so certificate validation can reach your domain.
You cannot change the domain yet
Each deployment can only change its assigned custom domain "once every 7 days". If you recently switched domains, the Branding page shows "Domain can be changed once every 7 days. Next change available on {date}." and the toast reads "Domain can only be changed once every 7 days."
Wait until the cooldown date passes, or continue using the currently assigned domain.
The domain is assigned to another deployment
A verified domain can only be assigned to one deployment at a time. If another deployment already uses it, the domain appears disabled in your "Branding" domain picker until it is unassigned elsewhere.
Shared links broke after a domain change
Changing or removing a custom domain invalidates existing public shared links for that deployment. After any domain change, republish or reshare workspace and gallery links so recipients get URLs on the new hostname.
Important
Plan domain changes during a quiet period. The confirm dialog warns that changing or removing the custom domain will invalidate all public shared links for the deployment.