If your custom domain shows an error page instead of your site, here’s what the common errors mean.
This error means your domain’s DNS is on Cloudflare, which can conflict with our Cloudflare-based hosting. RebelSites normally detects this automatically and routes your domain through an alternative bridge to avoid the issue.
If you’re seeing this error, it likely means the automatic detection happened after the domain was already added, or the bridge setup didn’t complete. Try disconnecting and re-adding the domain — RebelSites will detect the Cloudflare DNS and apply the workaround. If the error persists, tap the chat icon and we’ll fix it for you.
SSL certificates are provisioned automatically but take a few minutes after DNS propagates. What to do:
Wait 15–30 minutes. Most certificates provision within this window.
Verify your CNAME record is correct (check for typos).
Make sure there’s no conflicting A record pointing to a different IP.
If it’s been more than 2 hours, ping us in chat.
DNS hasn’t propagated yet, or the record is misconfigured:
Double-check the CNAME value matches exactly what’s shown in your RebelSites domain settings.
Try accessing the domain in incognito mode (your browser may be caching the old DNS).
Use whatsmydns.net to check if your record is visible globally.
You likely set up the CNAME for www but forgot the root domain redirect (or the other way around). Check your registrar for:
A CNAME record for "www" pointing to your RebelSites target.
A redirect or forwarding rule from the bare domain to www (or vice versa).
Still stuck? Hit the chat icon with a screenshot of your DNS settings and we’ll sort it out.
