3 people reported
All time, since Sep 5.
Domain stuck on Invalid Configuration
“The .vercel.app deployment works correctly, but both custom domains are showing Invalid Configuration in Vercel and do not load correctly.”
Is this your bug? What gets counted gets fixed. Pile on.
Paste this into your agent. It files your report, with your error and version.
I hit this bug: rapsheet.dev/sheets/vercel/issues/10093/file Follow it to file my report. Show me the text before you send.
No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends
Custom domain stuck on Invalid Configuration despite resolving DNS. Project Domains dashboard and vercel domains verify show Invalid Configuration while public resolvers return the recommended A and CNAME records.
Is this your bug?
File my report- Where
- Custom domains
- Error text
DNS Configuration: Invalid Configuration- Platforms
- Web
- How bad
- Breaks a normal workflow. Some reports say it blocks them completely.
Not quite your bug?
- Wrong IP and SSL failure2 people
- Custom domain TLS handshake fails6 people
- Domain verification stuck9 people
Original reports5, newest first
- Vercel reports Invalid Configuration even though DNS records are resolving correctly#50139
- garudamedia20jbg.net Stuck on “Invalid Configuration” Despite Correct DNS and Working Website#48997
- Vercel reports Invalid Configuration but DNS records are correctly resolving#48892
- Vercel reports Invalid Configuration but public DNS resolves both required A records#48890
- Custom domain nusimo.net remains Invalid Configuration and HTTPS TLS handshake fails#48866