Current versus Expected behavior:
Current:
-
Root domain
missionvillaja.comshows “Invalid Configuration” in Vercel dashboard for over 5 hours -
DNS A record is correctly configured to point to
216.198.79.1 -
Getting SSL certificate generation errors: “We could not generate a cert for missionvillaja.com because the required http-01 challenge failed. Timeout trying to solve challenge.”
-
When visiting missionvillaja.com, getting ERR_CONNECTION_TIMED_OUT
Expected:
-
Root domain should verify successfully and generate SSL certificate
-
Both
missionvillaja.comandwww.missionvillaja.comshould work with valid SSL
What’s Working:
www.missionvillaja.comis fully verified and working with valid SSL certificate
Code, configuration, and steps that reproduce this issue:
DNS Configuration (verified via Bluehost zone file):
A Record:
Name: @
Value: 216.198.79.1
TTL: 4 Hours
CNAME Record:
Name: www
Value: 173f78eb7a0b6159.vercel-dns-017.com
TTL: 4 Hours
DNS Verification:
-
Google Public DNS shows:
216.198.79.1(correct) -
Bluehost zone file shows:
216.198.79.1(correct) -
No conflicting CAA records
-
No _acme-challenge records blocking verification
-
Using Bluehost nameservers (not Vercel nameservers) with A/CNAME method
Steps taken:
-
Added
missionvillaja.comto Vercel project -
Added
www.missionvillaja.comto Vercel project -
Configured A record for @ pointing to 216.198.79.1
-
Configured CNAME for www pointing to 173f78eb7a0b6159.vercel-dns-017.com
-
Waited 5+ hours for DNS propagation
-
Clicked “Refresh” multiple times in Vercel dashboard
Issue: The www subdomain verified immediately, but root domain remains “Invalid Configuration” despite identical propagation time and correct DNS.

