Why is my custom domain not working?
A custom domain on TeleportHQ usually doesn't work for one of these reasons: the project isn't published to Production yet, the DNS records at your domain provider are missing, mistyped or still updating, an old record conflicts, or the workspace has no free domain slot. If the domain worked before and stopped, the trial or subscription may have ended. Find your symptom below.
Before you start
Open your project, click Publish at the top right, and find the Custom domain section. Most messages below appear there. When the project already has a domain, TeleportHQ checks it each time the Publish window opens ("Verifying configurations for …").
Problems while adding the domain
"Publish your project to production first — a custom domain always points at your live site, so there has to be one for it to reach." TeleportHQ can only connect a domain to a site that is live. Click Cancel, click Publish to Production, wait for Published, then click Configure again. See How to publish your site.
"This domain cannot be connected yet. Publish your project and try again." Wait until any publish in progress finishes, then try again.
"Invalid format/name" or "Enter a valid domain" Type only the domain, without https://, spaces or a slash at the end. For example mybakery.com or shop.mybakery.com.
"Domain is already assigned" This domain is already connected to this project. Click Cancel. The Custom domain section shows its status.
The "Purchase Custom Domain Subscription" window opens when you click Configure All custom domain slots in your workspace are in use. Remove the domain from a project you don't need, or buy a slot. See How many custom domains can I connect?.
"Subscribe to a paid plan for unlimited downloads, custom domains and public deployments." with an Upgrade Now button Your workspace's trial or subscription has ended, so custom domains aren't available. Subscribe to Pro or Premium. See How to subscribe to Pro or Premium.
"Something went wrong. Please try again or contact customer support." with a Retry button TeleportHQ couldn't add the domain. Click Retry. If an error message also appears, check what it says:
- "This domain is already set to another Vercel project": the domain is connected to another site hosted on Vercel, for example in another TeleportHQ project or your own Vercel account. Remove it there first, then try again.
- "This domain is already set for another Teleport Project": another TeleportHQ project uses this domain. Remove it from that project's Publish window first.
- "Domain was already added to a different project. Please complete verification to add it to this project instead.": add the TXT record TeleportHQ shows, then click Check status.
Problems while verifying
"Invalid Configuration" next to your domain The DNS records aren't set up yet, or haven't updated yet. Add the records in the Type / Name / Value table at your domain provider. Check for typing mistakes: the value must be exactly 76.76.21.21 for an A record, or cname.vercel-dns.com for a CNAME record. Wait a few minutes, then click Check status. DNS changes can take up to 48 hours. See Which DNS records do I need for my domain?.
"Remove the following conflicting DNS record from your DNS provider:" Your domain still has an old record, often from a previous website host or a "parked domain" page. Delete the record shown (find it by its type and value; its name may not be @), then click Check status.
A TXT record named _vercel appears in the table The domain has to prove it belongs to you. Add the TXT record with the exact value shown, keep the other records, then click Check status.
"Something went wrong. We were not able to verify your domain configurations. Please try again." The check itself failed. Wait a minute and click Check status again.
A message says "Could not verify custom domain" with "The provided custom domain is not associated with Vercel platform." TeleportHQ no longer finds the domain on your site, for example after a trial or subscription ended and the domain was removed. Click Remove domain, then connect it again from Configure.
Problems after the domain was connected
Only mybakery.com works, or only www.mybakery.com works You probably added only one of the two records. When you connect a root domain with a redirect, you need the A record for @ and the CNAME record for www. If you picked "no redirect", only mybakery.com is connected.
The domain shows an older version of the site Click Publish to Production again, with Publish to custom domain ticked in the footer of the Publish window, and wait for Published. A publish to Production with that box unticked goes live on your TeleportHQ address only, and your domain keeps the previous version. Publishing to Staging never updates your domain. Also see Why don't my changes show on my live site?.
The badge "Publish again to update search settings" appears Your domain setup changed after the last publish. Click Publish to Production so search engines index only your own domain.
The domain worked before and now shows nothing If the workspace's trial ended or the subscription was cancelled, TeleportHQ removed its deployments and custom domains. Subscribe again, publish to Production, then connect the domain again. See What happens when my trial or subscription ends?.
Visitors see a password prompt on the domain Password protection is on for the project, and it covers your custom domain too. On the trial, or in any workspace without a paid subscription, every publish is password-protected: share the password, or subscribe and then remove it. On Pro and Premium, someone clicked Enable. See How to password-protect your site.
Still stuck?
Copy the exact message from TeleportHQ and take a screenshot of your DNS settings, then write to hello@teleporthq.io. The team usually replies within 1 to 4 business hours.