Why my coaching domain shows a "site not configured" error

What "site not configured" actually means

You've set up your custom domain, shared the link with clients, and then — nothing. Instead of your beautiful coaching website, visitors (and you) see a cold, generic "site not configured" error. It's frustrating, but it's almost always fixable in under 10 minutes once you know what's causing it.

This error appears when the web server receives a request for your domain but can't match it to an active Coachful workspace. That mismatch can happen at three different layers: your DNS records, the domain configuration inside your Coachful dashboard, or an SSL certificate that hasn't finished provisioning yet. The sections below walk through every scenario.

TL;DR — Quick fixes to try first

• Check your DNS CNAME record points to proxy.coachful.co (not your old host, not a raw IP).
• Confirm the domain is saved in Coach Dashboard → Settings → Custom Domain.
• Wait for DNS propagation — changes can take up to 48 hours, though most resolve within 1–2 hours.
• Check SSL status — auto-SSL provisions automatically after DNS resolves; a pending cert shows a browser security warning, not the "site not configured" message specifically.
• Clear your browser cache and try an incognito window before concluding nothing has changed.

Step 1 — Verify your DNS records are correct

The most common reason a custom coaching domain shows a "site not configured" error is a missing or incorrect DNS record. Coachful requires a CNAME record (or an ANAME/ALIAS record for apex domains) that points your domain to Coachful's proxy infrastructure.

For a subdomain (e.g., coach.yourdomain.com)

1. Log in to your DNS provider (Cloudflare, GoDaddy, Namecheap, Google Domains, etc.).
2. Find the DNS management or "Zone Editor" section.
3. Look for an existing CNAME record for the subdomain you want to use (e.g., coach or www).
4. Set the Name to your subdomain prefix (e.g., coach) and the Value / Target to proxy.coachful.co.
5. Set TTL to Auto or 3600 (1 hour). Shorter TTLs speed up propagation during setup.
6. Save the record and wait. Use a tool like dnschecker.org to watch the propagation in real time.

For an apex/root domain (e.g., yourdomain.com)

Root domains can't use standard CNAME records — that's a DNS specification limitation. You have two options:

• Use your registrar's ALIAS or ANAME record (supported by Cloudflare as a "CNAME flattening" feature, and by Namecheap's ALIAS record type). Point it to proxy.coachful.co.
• Use a www subdomain instead (e.g., www.yourdomain.com) and set up a 301 redirect from the root to www at your registrar. This is the most universally supported approach.

Pro tip: Cloudflare users should set their CNAME proxy status to DNS only (grey cloud, not orange) during initial setup. Cloudflare's orange-cloud proxy can interfere with Coachful's SSL provisioning. Once your domain is verified and SSL is active, you can re-enable Cloudflare's proxy if you need its CDN benefits.

Step 2 — Confirm the domain is connected inside Coachful

Even perfectly configured DNS records won't work if Coachful doesn't know your domain belongs to your workspace. The platform needs to link the inbound request to your coaching account.

1. Go to your Coach Dashboard and click Settings in the left sidebar.
2. Select the Custom Domain tab (sometimes listed under "Website & Domain" or "Branding").
3. Enter your full domain — including the subdomain if applicable — in the custom domain field. For example: coaching.yourname.com or www.yourbrand.com.
4. Click Save or Connect Domain.
5. Coachful will attempt to verify the DNS record. You'll see a status indicator — Pending, Verified, or Error.

If the status stays on Pending for more than two hours after you've confirmed your DNS is correct, try removing the domain and re-adding it. This forces a fresh verification check.

Running a coaching business and want everything — your website, booking page, client portal, and messaging — under one branded domain? Coachful handles auto-SSL, CDN, and domain verification automatically so you spend your time coaching, not troubleshooting servers.

Step 3 — Check SSL certificate status

Coachful provisions a free SSL certificate automatically once your DNS is verified. This process typically takes 5–15 minutes after DNS has fully propagated. During that window, you might see a browser security warning rather than the "site not configured" error — but the two are sometimes confused.

Here's how to distinguish them:

• "Site not configured" — The request reached Coachful's proxy, but no workspace is mapped to this domain. Fix: complete Steps 1 and 2 above.
• Browser privacy/security warning (e.g., NET::ERR_CERT_COMMON_NAME_INVALID) — DNS is pointing correctly but the SSL cert is still provisioning. Fix: wait 15–30 minutes, then hard-refresh.
• DNS_PROBE_FINISHED_NXDOMAIN — Your CNAME record doesn't exist yet or hasn't propagated. Fix: verify the record at your DNS provider and wait.

If SSL hasn't provisioned after 2 hours and DNS is verified, reach out to Coachful support through the in-app chat. Include your domain name and a screenshot of the DNS record so the team can diagnose it quickly.

Step 4 — DNS propagation and caching issues

DNS propagation is one of those invisible delays that trips up even experienced tech users. When you create or update a DNS record, the change has to ripple across hundreds of resolvers worldwide. Depending on your registrar's TTL settings and your ISP's caching behavior, this can take anywhere from a few minutes to 48 hours.

While you're waiting, keep in mind that your DNS might have propagated for some people but not others — including you. A client across the country might see your coaching site load perfectly while you still see the error on your home broadband.

To test this without waiting:

1. Use dnschecker.org or whatsmydns.net to check if your CNAME is globally visible.
2. Open an incognito/private browser window to bypass local browser cache.
3. Try accessing your domain on a mobile device using cellular data (no Wi-Fi) to bypass your router's DNS cache.
4. Flush your local DNS cache: on macOS run sudo dscacheutil -flushcache; on Windows run ipconfig /flushdns.

Common mistakes and troubleshooting

Mistake 1 — Entering the wrong domain in Coachful settings

It's easy to type www.yoursite.com in the Coachful domain field but set up the DNS CNAME for coaching.yoursite.com. The two must match exactly. Double-check every character, including whether www is or isn't included.

Mistake 2 — Pointing the CNAME to the wrong target

Some coaches accidentally point their CNAME to their old website host or a Coachful subdomain like yourname.coachful.co instead of proxy.coachful.co. The CNAME target must always be proxy.coachful.co — that's the ingress point for custom domain routing.

Mistake 3 — Using an A record instead of a CNAME

Hardcoding an IP address via an A record is unreliable because Coachful's infrastructure IPs can change without notice. Always use a CNAME (or ALIAS/ANAME for the root domain). If your registrar only supports A records for the root, use a www subdomain with a CNAME instead.

Mistake 4 — Forgetting to remove the old host's DNS records

If you migrated from another platform, your DNS zone might still have old A records or CNAMEs for the same subdomain. Conflicting records cause unpredictable routing. Delete any old records that point to your previous host before adding the Coachful CNAME.

Mistake 5 — Checking the wrong domain in Coachful

Coachful workspaces also have a default {slug}.coachful.co subdomain. If your custom domain isn't working, your default subdomain always will. Confirm you're testing the custom domain specifically — paste it fresh into the browser address bar rather than clicking a saved bookmark that might redirect elsewhere.

Mistake 6 — Expecting instant results after saving DNS changes

DNS changes are never instant, even if your registrar's dashboard says "saved". Always give it at least 15–30 minutes before concluding something is broken. Set a timer, do a session with a client, and come back to check.

When to contact Coachful support

Most "site not configured" errors resolve themselves once DNS propagates and the domain is correctly saved in your workspace settings. But some situations need a helping hand:

• DNS has fully propagated (confirmed via dnschecker.org) but the error persists after 2+ hours.
• The Coachful domain settings panel shows Verified but the site still throws an error.
• You're using a registrar with unusual DNS handling (some enterprise or regional registrars use non-standard CNAME behavior).
• You've recently transferred your domain to a new registrar and the zone file didn't migrate correctly.

When you reach out, include: your custom domain, your Coachful workspace slug, a screenshot of your DNS records, and the exact error message or browser error code. That information lets the support team skip the basics and diagnose the real issue faster.

Pro tips for a smooth custom domain setup

Set up your custom domain before you go live — not after. DNS propagation delays are painless when your coaching program isn't launched yet. Scrambling to fix a broken domain link on launch day is a stressful experience you can avoid entirely.

A few other practices that prevent headaches:

• Lower your TTL before making changes. Set it to 300 seconds (5 minutes) a day before you plan to update your DNS. This means rollbacks and re-checks happen faster if something goes wrong.
• Keep a note of your old DNS records before deleting them. If the new setup causes unexpected problems, you can revert quickly.
• Test on multiple devices and networks — desktop, mobile, and someone else's internet connection — to confirm the domain is globally accessible before announcing it to clients.
• Use Coachful's default subdomain as a fallback. Your {slug}.coachful.co link is always live, so you can share that with clients in the interim while your custom domain propagates.

Ready to get your coaching domain live?

A "site not configured" error is almost never permanent. In the vast majority of cases, it comes down to a missing CNAME record, a domain that hasn't been saved in your workspace settings, or DNS propagation that just needs a little more time. Follow the four steps above in order and you'll have your custom coaching domain resolving correctly within a couple of hours.

If you're still setting up your coaching website or want to bring your own domain to a fully branded client experience — programs, booking pages, group squads, and all — start your free Coachful trial and have your site live today. Already a member? Sign in to your workspace and head to Settings → Custom Domain to connect your domain in minutes. For more setup guides, browse the full help center.