⌘K
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
specialthings The subscription became active on May 28 and renews on June 28, but the included monthly credits have never been provisioned. As a result, I am losing paid subscription time while being unable to use the credits included with the plan. Could this issue please be escalated? If the resolution takes longer, will there be any compensation for the lost subscription time?
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
usman please can you help as I am not so techy
usman Do we have any update on this? My site is not working.
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
Ryu Hi Priyanshu, A good way to approach sponsorship is to make the ask very concrete instead of asking generally for support. I would prepare a short sponsorship deck or one-page proposal with: Expected number of participants Audience profile, such as students, developers, founders, or AI builders Event date, format, and location/online details What sponsors get in return, such as logo placement, booth/demo slot, judging seat, workshop slot, social mentions, or access to project submissions Sponsorship tiers, for example venue/food/prizes/cloud credits/API credits Clear contact email and deadline
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.
Ryu Hi, Your CAA suspicion is worth checking. Vercel's domain troubleshooting docs say Vercel uses Let's Encrypt for automatic SSL certificates, and if any CAA records already exist on the domain, the domain needs to allow letsencrypt.org. A couple of things I would verify: Run: dig -t CAA +noall +ans bmudpt.xyz Confirm whether the domain has only pki.goog, or whether letsencrypt.org is also present. If CAA records are managed through Vercel DNS and you cannot remove/edit the pki.goog record, this may need Vercel staff to inspect the DNS zone. Also check the domain in Let's Debug or DNSViz, since
Ryu Hi Raymond, I can reproduce the syntax-error part in a basic v0 project. In app/page.tsx, if I temporarily leave JSX incomplete while editing, the editor becomes difficult/impossible to continue editing until the syntax is fixed or reverted. That makes normal incremental editing risky, because incomplete JSX is common while typing. A useful minimal repro seems to be: Open a v0 project. Edit app/page.tsx. Start editing a JSX line and leave it temporarily incomplete. Try to continue typing before the syntax is valid again. The editor can freeze or stop accepting normal edits. This feels like the
Raymond Please fix this problem ASAP, I'm really fed up with it lately 😤
Andrew 9507 Also, I'm seeing this as an issue when I visit the page. 502 Sandbox unreachable, restarting...
Andrew 9507 Also getting this as an error in the terminal 502: This sandbox is not listening on the requested port.Code: SANDBOX_NOT_LISTENINGID: iad1::mp7kj-1778524403602-f8fea3e21ed5
Ryu Hi Andrew, The key error seems to be: 502: This sandbox is not listening on the requested port Code: SANDBOX_NOT_LISTENING That usually means the preview sandbox started, but the app inside it is not serving on the port v0 expects, or the dev server failed before it could bind to the port. A few things I would check: Open the terminal/logs and look for the first error before the 502 message. Check package.json and make sure the dev script is normal for the framework, for example next dev. If this is a Next.js app, make sure the app is not hardcoding a different port. Avoid changing the dev ser
