system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Yuvraj2002 Yuvi I have already checked the DNS configuration. The apex domain uses: A @ → 216.198.79.1 The www domain uses: CNAME www → 779e5f4c88a8acd0.vercel-dns-017.com www.legaldocsmaker.in has a valid SSL certificate, but the apex legaldocsmaker.in remains stuck on "Generating SSL Certificate". Google Search Console reports "Invalid server SSL certificate". Could you please check the SSL provisioning for the apex domain?
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Jjuunnii98 4598 I also tried the account recovery form but it errors out repeatedly — is there another way to reach a human?
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Ryan Owens The Vercel Agent suggested I post here for resolution
Ryan Owens after looking at some other posts, it looks like other folks have had similar issues stemming from the deletion of an account (which is my situation as well) - I deleted a pro account that the domain must have been linked to that didn't transfer when i transferred the project. Here is some info about the domain: Paid January 16, 2026 Receipt number 2718-4286 Invoice number E90A26EE-0069
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Lauraborgenicht Dotcom @moderators Could you please delete this entire topic? It's my own post but it publicly ties my production domain to SSL details I'd rather not have indexed, and I'm past the window to edit or delete it myself. Much appreciated.
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Mclima Thank you for the troubleshooting guide. I reviewed the guide and ran the Vercel connectivity diagnostic as requested by Vercel Support. The diagnostic completed successfully from my location in Portugal. DNS resolution, HTTPS connectivity, the Vercel IP addresses, and the SSL certificate all appear to be working correctly. The issue I am trying to investigate is different from a typical domain configuration problem. The website works normally for me in Portugal, but my friend in McKinney, Texas, has been intermittently unable to access the website. Another person in the same location was also
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Amy Egan I wasn't able to replicate the issue you're seeing with that IP. Maybe specific to your ISP or location? There's a connectivity debugging guid with some steps that can give us more clues about what's going wrong. Can you try this and let me know what you find? vercel.com/kb/guide/troubleshooting-connectivity-issues
Ellach Since DNS resolution is correct and consistent, the failure must be happening at the TCP/TLS connection itself, not name resolution. This matches what I found earlier with a direct openssl test: the connection reaches an IP in this range but the TLS handshake fails with "wrong version number" — meaning something is corrupting the handshake between my network and your edge, not a DNS problem. Can your team check TLS behavior specifically for 64.29.17.0/24 and 216.198.79.0/24 from an external vantage point?
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
Amy Egan It's asking for TXT record to verify that you're not stealing someone else's domain. careerai.qd.je is a subdomain, so the verification record needs to be associated with the root domain. That's why it's expected to be on _vercel.qd.je for verification to succeed. Instead, you can use the free *.vercel.app domain provided by Vercel, choose from one of the other free domain providers using recognized public suffixes, or buy your own custom domain. I hope that helps!
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Amy Egan Just tested it and saw it's returning a 404 with code NOT_FOUND rather than DEPLOYMENT_NOT_FOUND. That means the deployment exists, but the page you expected doesn't. Please use the debugging steps linked above to figure out why that's happening
system The domain troubleshooting guide can help with most custom domain configuration issues. You might be able to use that guide to solve it before a human is available to help you. Then you can come back here and share the answer for bonus points. vercel.com/docs/domains/troubleshooting
mathew jhones I’ve run into a similar issue with custom domains. Sometimes the old configuration or CDN cache can take longer to clear even after removing the domain. Checking the DNS records and waiting for propagation usually helps.