Why can't I publish my app to my custom domain?

There are a few common reasons an app won’t publish to a custom domain. The most likely issue depends on where you’re hosting it and how the domain is set up, but here are the usual blockers:

Common causes

1. DNS not pointing correctly

   • Your domain’s DNS records may not be set to the hosting provider’s required values.
   • For example, you may need a CNAME, A record, or verification TXT record.

2. Domain ownership not verified

   • Some platforms require you to prove you own the domain before publishing.

3. SSL/TLS not fully provisioned

   • The site may be configured, but HTTPS can’t be issued yet because DNS hasn’t propagated or the domain setup is incomplete.

4. The domain is already in use elsewhere

   • Another app or service may already be attached to that domain or subdomain.

5. Wrong subdomain/root setup

   • Publishing to example.com vs www.example.com often requires different DNS records.
   • Root/apex domains sometimes need special support like ALIAS/ANAME or provider-specific flattening.

6. Propagation delay

   • DNS changes can take minutes to 48 hours to fully propagate, though often it’s much faster.

7. Platform restrictions

   • Some app builders only allow custom domains on paid plans, or require a specific deployment state before enabling them.

What to check

• Confirm the exact DNS records your hosting platform asks for.
• Make sure there are no conflicting records for the same domain.
• Wait for DNS propagation if you just made changes.
• Check whether your app/platform has a custom domain verification step.
• Verify that your domain is not already connected to another site.

If you want, I can help troubleshoot it

Send me:

• the platform you’re using
• the exact error message
• whether you’re using www or the root domain
• your current DNS records (you can redact sensitive parts)

…and I can tell you what’s wrong.