The latest update has really degraded the user experience. Previously, it was a fantastic tool for frontend prototyping with a reliable preview. This new ‘box’ setup has made the preview feature almost unusable. It feels like they over-engineered a solution that was already working well
Subject: v0 Previews Failing to Boot - 502s, CORS, and (blocked:origin) on vusercontent
The Issue: > Whenever I generate a UI or bring a template from the Marketplace into my chat/project, the dedicated preview environment completely fails to load. Some of the Community Templates/Marketplace previews work fine, but some do no. My specific workspace containers always crash on startup. Have not seen one preview in my project yet. I literally just bought it yesterday, and a bit frustrating.
Console Errors:
Unsafe attempt to load URL https://vm-[REDACTED].vusercontent.net/ from frame with URL chrome-error://chromewebdata/. (The container fails to load, triggering the internal browser error and a CORS conflict).
Multiple (blocked:origin) errors for vm-[REDACTED].vusercontent.net.
Multiple 502 Bad Gateway errors when the environment attempts to fetch extensions from open-vsx.org.
Troubleshooting Already Completed:
Tested in both Chrome and Firefox (issue persists).
Tested on my home wired and wireless network ( AND disconnected and tested via a Cellular Mobile Hotspot (issue persists).
No VPNs, custom DNS, or strict browser extensions are active.
Because this happens across distinct browsers and entirely different ISP networks, it appears my v0 workspace containers are failing to provision or connect on Vercel’s backend.