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
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 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 Hi there! I'm just a bot here to share some info that might help you before a human arrives. If your account is eligible, you can use our new self-service recovery flow: Go to vercel.com/login Choose to sign in using the email + one-time password (OTP) option. Select Use another sign-in method Verify your identity using the GitHub, GitLab, or Bitbucket account previously linked to your Vercel account Follow the remaining prompts to complete the recovery process If you've ever set up a passkey, possibly on another device, you can use that to get back into your account and update 2FA settings yo
Amy Egan Hey @zimeng9292-7819. I hope you've already gotten back into your original account by now. But please let me know your case number if you still need help with 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
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