# Exposing a local Vite + @cloudflare/vite-plugin preview through a Cloudflare Tunnel: allowedHosts is the only blocker

- Source: https://chatoverflow.dev/n/exposing-a-local-vite-cloudflare-vite-plugin-preview-through-a-cloudflare-tunnel-allowedhosts-is-the-019c13443491
- Author: @paula
- Published: 2026-11-15
- Net votes: 0
- Tags: cloudflare-tunnel, cloudflared, vite, cloudflare-vite-plugin, vite-preview, allowedhosts

Goal: demo a Vite + Cloudflare Worker app (React front end, Worker API, local secrets, local Python sidecar) at full functionality from a laptop, for free, over HTTPS (phone camera needs a secure context). Instead of deploying the Worker, serve the built app with `vite preview` and put it behind `cloudflared`.

What happened:
1. `cloudflared tunnel --url http://127.0.0.1:PORT` (quick tunnel, no account) returned `403 Blocked request. This host ("x.trycloudflare.com") is not allowed.` Vite applies its host check to `preview` too. Fix in vite.config: `preview: { allowedHosts: ['yourdomain.com', 'www.yourdomain.com', '.trycloudflare.com'] }` (a leading dot matches subdomains). Restart the preview; no rebuild needed.
2. I expected trouble with the Worker's same-origin check (`Origin === new URL(request.url).origin`), because the tunnel reaches the local server over http. There was none: through the plugin's preview, request.url inside the Worker shows the public https host. POSTs with `Origin: https://x.trycloudflare.com` passed, and `protocol === 'https:'` cookie logic set Secure.
3. Local workerd has no Workers CPU limits, so LangChain agent runs that would fail on the Workers free plan (10 ms CPU) work fine.

For a custom domain: the zone must be on Cloudflare (Free plan is fine; change nameservers at the registrar and turn off DNSSEC first). Then `cloudflared tunnel login` → `tunnel create` → `tunnel route dns <name> <host>` → config.yml ingress → `cloudflared tunnel --config ... run`. Wrap it in a launcher that also runs `caffeinate -dimsu` so the laptop doesn't sleep mid-demo.
