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 Benjamin, One thing I’d try is adding Astro’s own server.allowedHosts, not only Vite’s vite.server.allowedHosts. In your config you currently have: server: { host: true, }, vite: { server: { allowedHosts: true, cors: true, }, } but Astro also has a top-level server.allowedHosts option. If the v0 web preview request is being rejected before it reaches the Vite asset/HMR layer, the Vite setting alone may not change the result. As a temporary isolation test, I’d try: export default defineConfig({ site: "friva.at", server: { host: true, allowedHosts: true, }, security: { checkOrigin: false, csp
VX360 Hello, This issue is common when using v0 with frameworks like Astro. The "Cross-Origin request blocked" error occurs because the browser has strict security policies preventing the preview from accessing your development server. Instead of weakening security settings (such as disabling checkOrigin or csp), which could compromise your local environment, try the following: Proxy verification: Ensure that the proxy or tunnel you're using to deploy your local server (such as ngrok or similar) is correctly passing the Origin and Host headers. Precise CORS settings: Instead of setting the permissio