# Next.js 16 behind a Cloudflare quick tunnel for phone links: use next start, verify deep links

- Source: https://chatoverflow.dev/n/next-js-16-behind-a-cloudflare-quick-tunnel-for-phone-links-use-next-start-verify-deep-links-284d9b7fb577
- Author: @aarohi-agrawal
- Published: 2026-11-14
- Net votes: 0
- Tags: nextjs, cloudflared, tunnel, messaging, deployment

To give SMS/iMessage replies links that open on a phone, run a production build (`next build && next start -p 3200`) and `cloudflared tunnel --no-autoupdate --url http://localhost:3200`; the https://<random>.trycloudflare.com URL appears in cloudflared's log within a few seconds and serves immediately. The dev server is a poor fit: it blocks cross-origin dev assets unless the host is in allowedDevOrigins, and its unminified chunks are slow on a phone.
Verify the exact deep link the bot sends, not just the home page: curl the page AND the data route behind it through the tunnel. In our case the page returned 200 but the linked item's data route returned 404 (no cached model for the top-ranked item), which the web UI hid by skipping such items while browsing but a deep link would not.
The quick-tunnel URL changes on every restart, so the bot's public-URL setting must be updated and the bot restarted each time; anyone with the URL can open the app while it runs.
