PJ
Hey โ€” I'm PJ ๐Ÿ‘‹
Real help, no runaround.
Text me ๐Ÿ“ฑ
SideGuy Fixables ยท Real Human Clarity ยท Apr 2026

Custom domain shows
an error or blank page.

The two most common causes: the CNAME file got deleted from the deploy output, or DNS records haven't propagated yet. Both are fixable in minutes.

๐Ÿ’ฌ Text PJ โ€” diagnose it live

Check these two things first

1. Go to your repo on GitHub โ†’ Settings โ†’ Pages. Is the custom domain still listed? If it disappeared, the CNAME file was overwritten by a deploy. 2. Run nslookup yourdomain.com โ€” if it doesn't return your host's IP, DNS hasn't propagated yet (wait up to 48 hours).

Common causes & fixes

CNAME file overwritten

Your build script is deleting _site/ and rebuilding. The CNAME must be copied into _site/ every build โ€” not just the repo root.

DNS not propagated

New DNS records take 1โ€“48 hours. Use nslookup or dig to check current resolution. Nothing to fix โ€” just wait.

Wrong CNAME record

For GitHub Pages: CNAME should point to username.github.io not the repo URL. Check your DNS provider settings.

SSL cert not issued

After pointing your domain, GitHub takes a few minutes to issue a cert. Wait 10โ€“15 min, then check Settings โ†’ Pages for the HTTPS option.

Make sure CNAME is copied on every build:

# Your build script must copy CNAME every time:
[ -f CNAME ] && cp CNAME _site/CNAME

# Verify it's there after building:
cat _site/CNAME
Domain still not resolving?

Clarity before cost. Real help. No runaround.

Text PJ โ€” 858-461-8054
Related fixes SSL Certificate Error GitHub Pages Not Updating โ† All Fixables
PJ
Hear PJ
โ–ถ tap to listen
Text PJ
Text PJ

What should you do next?

Real Situations We See

What Happens After You Text