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.
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.
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.
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.
SkyMesh Dynamics ah, then I'm not the only one who reported this
Ryu Hi Yuze, Your openssl test is a good way to narrow it down. Since this fails when the trailing dot is included in SNI: but works without it: then this is happening before your Next.js app or vercel.json redirects can run. So I don’t think there’s an app-level redirect/header fix for the HTTPS case. A trailing dot is valid in DNS as an absolute/FQDN form, but TLS certificate/SNI matching is a separate layer. If Vercel’s edge does not normalize deckclip.app. to deckclip.app before selecting the certificate, the handshake can fail before any HTTP request exists. The practical workaround is to avo
Ryu Hi Den, TLS 1.3 and HTTP/3 are related, but they are not the same thing. TLS 1.3 means the HTTPS handshake can use the newer TLS version. HTTP/3 specifically means the site is being served over QUIC/UDP instead of HTTP/1.1 or HTTP/2 over TCP. A quick way to test what your site is actually negotiating is: or in Chrome DevTools: If you see h2, that is HTTP/2. If HTTP/3 is active, you’d usually see h3. From the current Vercel docs I can find, Vercel explicitly documents TLS 1.2 / TLS 1.3 support, but I don’t see HTTP/3 listed as a supported CDN protocol yet: vercel.com/docs/cdn-security/encryptio
Den.D Hi @ryux1 , thanks fro the reply. You hit the nail on the head. As I mentioned in my post, even though the two things aren't directly connected, I don't understand the logic of supporting only TLS 1.3 and not HTTP/3. This is especially true when even the cheapest shared hosting providers ($10–$20/month) offer HTTP/3 by default. Of course, there's no personal setting for that, being a platform lack... My post was just a rant, hoping that someone in Vercel reads it and acts to solve the gap 🙂
Ryu Hi Den, Yep, fair point. I mostly replied to clarify the TLS 1.3 vs HTTP/3 difference for anyone else reading the thread. I agree there probably isn’t anything to configure at the project level right now. It would be nice to have HTTP/3 support on Vercel too, or at least a clear note in the docs about the current status. Thanks for raising it.