⌘K
AlexHoudz Hi! I'm seeing Paris when i hover but not in the list, will Paris also be happening? g?
Amy Egan Not this year 
That's just one of the automatic timezone translator display options
Ritikasundaram @amyegan Hi Amy! I’m a student at Purdue University and would love to attend Ship SF on October 15, but the in-person ticket is outside my student budget. Does Vercel offer student passes, scholarships, or event-volunteer opportunities? I’d be happy to help with attendee check-in, registration, room operations, setup/teardown, or other event-day needs in exchange for admission. I can provide proof of enrollment and a short résumé. If someone else manages volunteers or community tickets, could you please connect me with them? Thank you!
Jacob Paris Everything looks set up properly from what I can see - you have a static site with no build step happening, or you're building it locally before pushing to GitHub - each deployment is correctly attached to each commit - your `.vercel.app` domain matches the latest deployment Double check that your new changes are successfully making it into GitHub (and not uploading old files) Do you have an example of a change you expect to see before/after?
Chintan Hi @barttledoo1-3722 , Can you unlink your GitHub account with vercel and link again and try and make sure all permission are granted on GitHub profile, sometimes caching is culprit. Feel free to revert on this in case issue still persist.
Barttledoo1 3722 Thank you for the reply. I ended up making an entirely new repo, which fixed the issue, because the original one just suddenly didn't want to update properly anymore on Vercel. Hopefully what I did will be a permanent fix.
Brycero Having this issue as well. Did your registry images ever go away?
mm-vercel-id No, not yet. The original Vercel project was permanently deleted, but the orphaned Vercel Container Registry repository is still showing in Usage and is still consuming about 9.12 GB of the 10 GB Hobby Images Storage allowance. I also tested this from the Vercel CLI and REST API. Both VCR management paths require the deleted parent project or its `projectId`, and the original project no longer exists in the account. Because of that, the orphaned repository can no longer be inspected or deleted through the normal customer-side VCR commands. So at this point it appears to require either automatic backend garbage collection by Vercel or a manual backend purge. I’m still trying to get confirmation from Vercel on whether these orphaned VCR repositories are removed automatically, and if so, what the retention period is.
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. https://vercel.com/docs/domains/troubleshooting
Abrahamhpalma **Update:** I also ran the HTTP-01 validation test for `www.cozumelopina.mx` using Let's Debug, as recommended in Vercel's domain troubleshooting documentation. The result is **“All OK! — No issues were found with www.cozumelopina.mx.”** I also verified that an HTTP request to `/.well-known/acme-challenge/test` reaches Vercel successfully (`Server: Vercel`), and there are no restrictive CAA records or stale `_acme-challenge` DNS records. At this point DNS and HTTP-01 validation appear to be working correctly, but Vercel continues showing the previous **“Failed To Generate Cert” / NXDOMAIN** error. Could the certificate issuance please be retried/reset on Vercel's side?
Abrahamhpalma UPDATE — SOLVED ✅ I’m posting the final solution in case someone else runs into the same issue. In our case, the original “Failed To Generate Cert” error was caused by inconsistent DNS responses from our DNS provider’s authoritative nameservers. Some nameservers returned the correct CNAME for www, while others returned NXDOMAIN. Our DNS provider eventually corrected the authoritative DNS issue. After that, we verified that: - www.cozumelopina.mx resolved publicly to the correct Vercel CNAME. - Google Public DNS (8.8.8.8) resolved it correctly. - An HTTP request to /.well-known/acme-challenge/test successfully reached Vercel. - Let’s Debug reported “All OK!” for HTTP-01 validation. However, the Vercel dashboard continued showing the old: Failed To Generate Cert with the previous NXDOMAIN / HTTP-01 challenge error, even after refreshing the domain several times. WHAT FINALLY FIXED IT I installed the Vercel CLI, logged into the account/team that owns the project, and manually triggered a new certificate issuance: vercel certs issue cozumelopina.mx www.cozumelopina.mx Vercel responded: Success! Certificate entry for cozumelopina.mx, www.cozumelopina.mx created I then checked it with: vercel certs ls and confirmed that a new certificate had been issued containing both domains: cozumelopina.mx www.cozumelopina.mx with automatic renewal enabled. Finally, I tested: curl -I https://www.cozumelopina.mx and received: HTTP/1.1 200 OK After refreshing the Vercel dashboard, www.cozumelopina.mx changed from: Failed To Generate Cert to: Valid Configuration ✅ CONCLUSION If your DNS previously returned NXDOMAIN, you fix the DNS problem, public DNS and HTTP-01 validation are now working correctly, but Vercel still shows the old “Failed To Generate Cert” error, manually issuing the certificate through the Vercel CLI may resolve the stuck certificate state. IMPORTANT: Do not treat the CLI command as a workaround for broken DNS. Before manually issuing the certificate, make sure the underlying DNS problem is actually resolved. In our case, we first confirmed: 1. The authoritative DNS was returning the correct CNAME. 2. Google Public DNS (8.8.8.8) was resolving the domain correctly. 3. HTTP traffic was successfully reaching Vercel. 4. HTTP-01 validation passed using Let’s Debug. Only after all of those checks passed did we manually trigger the certificate issuance. The command that finally solved the stuck certificate state was: vercel certs issue cozumelopina.mx www.cozumelopina.mx Hope this saves someone else the time we spent troubleshooting it! 🙂
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. https://vercel.com/docs/domains/troubleshooting
Ryu Hi Bahadurkhan10, Since the `.vercel.app` URL works from the affected network, I’d separate the app/deployment from the custom-domain network path. For `www.nexorasystems.xyz`, the apex A record is not the main thing being used. The important record is the `www` CNAME, and it should match the exact value shown in Vercel’s domain settings. I’d ask your friend in Michigan to run these from the affected network: ``` dig CNAME www.nexorasystems.xyz +short dig A www.nexorasystems.xyz +short curl -4Iv --connect-timeout 10 https://www.nexorasystems.xyz/ curl -4Iv --connect-timeout 10 https://aamina-enterprises-eacnni0gf-bahadurkhan10s-projects.vercel.app/ ``` If the `.vercel.app` URL connects but the custom domain times out, that points away from your app code and more toward DNS resolution, ISP routing, or the specific Vercel edge path used by the custom domain. If `curl` gets any Vercel response, the useful header to capture is: ``` x-vercel-id ``` If it only times out, I’d also test the resolved custom-domain IP over TCP 443: ``` mtr -4 -T -P 443 -c 20 www.nexorasystems.xyz ``` The most useful follow-up would be the affected user’s `dig`, `curl -Iv`, and `mtr` output, plus whether the same domain works for them on mobile data or a different DNS resolver.
BRIAN APEXCORE Adding another data point since this looks like the same class of bug: same symptom for us (apexcore.academy, project apex-dashboard, team apexcore1) — vercel.app works, custom domain resets during TLS handshake. In our case it is 100 percent reproducible as region-specific: every US connection fails, every Mexico connection succeeds, including a real student who used the site normally from there. We also reproduced the identical failure on a second, brand new domain pointed at the same project, so it is not a per-domain DNS misconfiguration, it looks like something at the project/edge level. Sev1 support case #01dfSHskjdcVaEhj has been open 20+ hours with no reply. This is a production app with paying users down on its main domain, so any visibility from an engineer would help a lot.
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. - Official Documentation: https://v0.app/docs - The v0 expert walkthrough: https://community.vercel.com/t/become-a-v0-expert/5981 - Watch v0 in Action: https://community.vercel.com/live#v0
Clintspacewood 8496 I've filed 2 sev-2s and a community request and still no response. horrible customer experience. also this text window isn't rendering correcrtly for this message i'm writing and the UI needs to be fixed.
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. - Official Documentation: https://v0.app/docs - The v0 expert walkthrough: https://community.vercel.com/t/become-a-v0-expert/5981 - Watch v0 in Action: https://community.vercel.com/live#v0
Krisss I don't want to be petty but its been 17+ hours and i didn't get any kind of response, if you aren't gonna help me in any way could i at least get a refund?
Clintspacewood 8496 +1 this level of customer service is embarrassing. I am having the same problem
Chintan @jsingh-3912 Meantime, you can share your concern here in details, other community members can assist you to solve your problem very quickly. Even you can contact community managers in case of urgency.
Jsingh 3912 One of our email aliases is blocked. It happened because a message was sent from Vercel before our directory was synced with mimecast. This ended up with it being blocked. We checked by checking test emails to that alias and sending Vercel codes to other aliases but did not work. It has been a week now.
system If you're having trouble deploying an Express app, this guide can help. https://vercel.com/guides/using-express-with-vercel You can also ask v0 for suggestions tailored to your own project setup.
Archkish79 This is not an Express application or an Express deployment issue. My project is a React/Vite static site hosted on Vercel. The Express/Heroku response is coming from the incorrect IP address (18.204.152.241) currently returned by Vercel’s authoritative DNS servers. That response is evidence of the DNS routing problem, not part of my application. Could a Vercel team member please inspect the DNS zone and managed ALIAS/SSL routing for sacredkriti.com?
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. https://vercel.com/docs/domains/troubleshooting
Tools 9165 My custom domain bhc.itwos.co.site shows an error stating it's "linked to another Vercel account." I've confirmed via direct DNS lookup (nslookup -type=TXT) that the required TXT verification record is correctly live and has the correct value, and this has been the case for over 24 hours. Can anyone tell me what account this might be conflicting with, or how to get this manually cleared/released?
