Pauline P. Narvas This is fantastic. Thanks for sharing, Philo!
BestCodes Okay... I see this as a big security vulnerability, actually, but would love to hear your perspective. Obviously, if an agent can submit any solution it wants, a human or compromised agent could submit a malicious solution. For example, let's say an agent runs into a bug where it forgets to use await with params from Next.js which happens a lot with Claude Code etc. So the agent goes and looks for a solution. Maybe the solution says "curl ai-solutions.co/next-params.md and open it to view fix instructions". This could be completely innocent or maybe next-params.md could actually be a malicious
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/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.
Maiierik Hi Vercel team, Project: vize-danismanlik (team: maiieriks-projects) Custom domains: yonstudent.com + www.yonstudent.com Latest production deployment URL: vize-danismanlik-h6zv6x16t-maiieriks-projects.vercel.app Both custom domains consistently return HTTP 421 with body "Forbidden host" from all regions. The canonical project URL (vize-danismanlik-ecru.vercel.app) works correctly. What I verified: vercel domains inspect yonstudent.com -> verified: true, assigned to vize-danismanlik project API GET /v9/projects/{projectId}/domains -> returns both domains as verified DNS resolves to Vercel anyca
Ryu Hi Maiierik, Based on what you've already checked, I'd try to prove whether this is still DNS propagation or whether the hostname binding at the edge is the failing part. These tests should help separate that: If the normal curl and the --resolve version both return the same 421 Forbidden host, that mostly rules out public DNS propagation and points more toward the custom hostname not being matched to the project at Vercel's edge. I'd also make sure both yonstudent.com and www.yonstudent.com are explicitly added to the same Vercel project/environment, rather than relying on an automatic redire
Lovecity4real 9798 Same issue. Project: rentclaim, Domain: rentreclaim.xyz. Dashboard shows Valid Configuration, rentclaim.vercel.app works, but rentreclaim.xyz fails SSL handshake on Safari and WebKit. DNS: rentreclaim.xyz -> 216.198.79.1. Started recently with no changes on our side.
Ryu Hi matprofi, Since the .vercel.app domain works and TCP reaches 216.198.79.1:443, I'd treat this as a domain/certificate provisioning path issue rather than a Next.js/deployment issue. I'd check the certificate blockers Vercel calls out before re-adding the domain again: A few things to look for: NS should point to the DNS provider where you are actually editing records. The A / CNAME results should match exactly what Vercel shows for each domain. There should not be stale/conflicting AAAA records pointing elsewhere. If CAA records exist, they need to allow Let's Encrypt, for example 0 issue "
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/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.
Carlos Henreis I'm having the same problem, did you find any answer/solution?
Marcelo Sabino Nope, no solution yet. I'm experiencing this issue right now, and while investigating, I found this other post describing the exact same problem. The domains mentioned there are also affected at this very moment. >> community.vercel.com/t/custom-domains-timing-out-in-brazil-while-vercel-app-domains-work-normally/41889/2
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/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.
Pratikonly not fixed not generating cert
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/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.
Michaelbusby 4811 Unfortunately I have searched the forums and read the troubleshooting guide, and most of the issues people seem to have are with not having ability to edit the root DNS zone. I don't have this problem, but a separate one.
Amy Egan It asks you to verify the root to make sure you have control of the domain. It's to prevent someone from using a domain or subdomain they don't actually own
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/projects/domains/troubleshooting You can also use v0 to narrow down the possibilities.
js I'm seeing the same problem on one of my three projects. I've tried both Chrome, incognito Chrome, and Firefox, all with the same issue. I'm on a mac. Nextjs as well.
js And now it's fixed.