⌘K
Nygel Its pretty insane how much money I already lost on this.
Mindset of Champions If we go by token cost alone, it's a 5x cost increase at best any time it occurs (although probably much more in practice). I hope it's addressed.
Nygel They got me again, on a minor change on the app. Didn't need a v0 Max for that. Just burned through all my credits. I'm so done with this.
Amy Egan It looks like you got it working. Both URLs seem to go to the same site at the moment. Do you still need help with this?
Eldargvideo 8087 Vercel’s managed apex ALIAS is serving a stale flatten. Your proof that hitting 216.198.79.1 / 64.29.17.1 serves the right deploy is the diagnosis. Put explicit A records to those two IPs at the registrar (keep MX/TXT), or move DNS off Vercel nameservers and CNAME www + ALIAS apex to cname.vercel-dns.com.
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. Official Documentation: v0.app/docs The v0 expert walkthrough: community.vercel.com/t/become-a-v0-expert/5981 Watch v0 in Action: community.vercel.com/live#v0
jieun Downloading the ZIP file just shows 0 bytes 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 While a member of our team prepares to jump in, you might find your answer even faster in our community resources. Official Documentation: v0.app/docs The v0 expert walkthrough: community.vercel.com/t/become-a-v0-expert/5981 Watch v0 in Action: 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.
Amy Egan Can you let me know your case numbers? I'd like to look into this
system While a member of our team prepares to jump in, you might find your answer even faster in our community resources. Official Documentation: v0.app/docs The v0 expert walkthrough: community.vercel.com/t/become-a-v0-expert/5981 Watch v0 in Action: community.vercel.com/live#v0
Amy Egan It looks like the support team was able to get you a refund a few days ago. But please let me know if you still need help with this
Ryu Hi Tilanddi, Since the Deploy Hook can create a Production deployment, I’d first separate “Vercel can build the project” from “GitHub events are allowed to trigger deployments.” A few non-sensitive checks I’d make: Then check the repo at that commit for either of these: or a branch rule like: git.deploymentEnabled can disable automatic Git deployments even if the GitHub app is still connected, so it’s worth ruling out separately from the dashboard “Ignored Build Step” setting. I’d also check Project Settings → Git for “Require Verified Commits.” If that was enabled recently and the merge commi
Tilanddi Prog Hi, Thanks for the pointers — I went through all of them. Here's what I found, ruling out each one: vercel.json / git.deploymentEnabled: Checked both the current branch and the exact merge commit that's live in Production (412467a02250f14b7100f933b8f02eabb206108c). No git key at all in vercel.json — no deploymentEnabled: false, no per-branch rule. Ignored Build Step: Set to "Automatic" (the default — skip only if the exact commit SHA was already deployed). Not customized. Require Verified Commits: "Inherit from Team (Disabled)". Not the cause. Classic repo webhook: None configured on the GitHu
Ryu Hi Tilanddi, Thanks for checking all of that. Just to clarify, I’m not Vercel staff, so I can’t inspect internal GitHub App delivery logs or deployment queue logs for the project from here. One config check I’d still make is the legacy key, because it is separate from the newer git.deploymentEnabled setting: Specifically look for this exact shape anywhere in vercel.json or vercel.ts: That key is deprecated, but Vercel’s docs still describe it as disabling Vercel for GitHub deployments, and the Deploy Hooks docs mention that deploy hooks will not trigger when github.enabled = false is present:
