Belty6979 5979 This is a really interesting use case. A native iOS client for managing deployments and checking project status would be genuinely useful, especially when you’re away from a laptop. The OAuth + PKCE approach also sounds like a much better experience than asking users to manage API tokens manually. Hope Vercel opens up the permissions beta soon.

Ryu Hi Pjmathur0291, For an HTTP-01 validation failure, I’d check the DNS and certificate-blocking records before assuming it needs a manual certificate flush. From a terminal, I’d run: A few things to look for: Vercel’s domain troubleshooting guide covers those SSL checks here: vercel.com/docs/domains/troubleshooting If all of those are clean and the dashboard still shows HTTP-01 failure, the useful details to share are the exact domain status from Vercel, the dig output above, and the timestamp when you retried certificate generation.

Wjh6548 4228 yeah, so am i. So I couldnt finished my rest assignment. how am i supposed to do??

Ryu Hi Bradley, Failed to prepare VM sounds like v0 is failing before it can fully start the sandbox/preview environment, so I’d first separate a broken project from a broader v0/account/platform issue. I’d test these in order: If it happens only on one project, the project may have something that prevents the sandbox from starting, like an install script that hangs, a dependency conflict, a very large generated file, or a command that never exits. If it happens on every new blank project too, then it is probably not your app code. In that case the useful public details to share are: I would avoid

atahf Hi Vercel Team! I'm having the same problem, can someone look into this? Team ID: team_H8Rsw11fVMF2qEUaPptIUW2q ps. I had a quick look in community posts and this issue seem to be happening quite often for most of Hobby plans

spanishkangaroo Hi! Same from my side. I just added the credit card today. Everything seems ok and I even got the 5$

Ryu Hi Abdelaziz, Since it works from personal devices and mobile but fails only on corporate devices with DNS_PROBE_FINISHED_NXDOMAIN, I’d first treat this as a DNS resolution issue on the enterprise network, not a Vercel deployment problem. Ask someone on the affected corporate network to compare the corporate resolver with a public resolver: or: What the results mean: If only the enterprise DNS returns NXDOMAIN, the fix usually has to come from their IT/network team. They may need to clear DNS cache, allowlist the domain, or check whether a security product is blocking newly registered/uncatego

Amy Egan After the high usage falls off from the rolling 30 day window, Vercel Agent can help you unpause the team 😃 community.vercel.com/t/my-account-is-still-paused-even-after-low-usage/43354/2

Amy Egan Serverless architecture is at the heart of Vercel. All of our services rely on that energy-efficient alternative to traditional servers. It's better for the environment and it helps keep things affordable. Vercel uses multiple cloud providers that have made commitments to reducing their overall carbon footprint. However, use of servers around the world with multiple providers means we can't reliably calculate and prove our carbon footprint. vercel.com/kb/guide/what-is-vercel-green-energy-policy

Ryu Hi Zenyxmed, Since Vercel is still asking for _vercel.synedica.de, I'd first verify what the public authoritative DNS actually returns, not only what Cloudflare shows in the dashboard. Try these: A few things I'd check: The NS output should point to Cloudflare nameservers. If the registrar is still delegated somewhere else, the Cloudflare records will not be seen by Vercel. The TXT output should exactly match the current value Vercel shows after the most recent time you added the domain. If you deleted/re-added the domain, Vercel may have generated a new verification value, so an older _vercel

Theostafford7 3647 This looks like a Vercel SSL provisioning issue rather than a DNS problem. Since HTTP is routing correctly but HTTPS fails during the handshake, Vercel support should check whether certificate issuance or domain verification is stuck on their side.

Ryu Hi Jufriadi, Since HTTP is already reaching Vercel but HTTPS fails and the dashboard still says Invalid Configuration, I'd double-check the records that can block SSL provisioning rather than the app itself. A few things to verify at the DNS provider: For the apex domain, the A record should match exactly what Vercel shows in the Domains dashboard. For www, the CNAME should also match exactly, including any trailing . if your DNS provider requires it. Also make sure there are no AAAA records pointing somewhere else, because Vercel's troubleshooting docs note that IPv6/AAAA records are not supp

Amy Egan I usually start with browser dev tools and Vercel runtime logs. From there, it depends on what's going wrong. Instant rollback can help when you want to get Production working again but you're not able to find and solve the production issue quickly

Wise Lizard Update: seems to be resolved now