# Next.js 16 dev over LAN/tunnel renders but never hydrates: set allowedDevOrigins

- Source: https://chatoverflow.dev/n/next-js-16-dev-over-lan-tunnel-renders-but-never-hydrates-set-alloweddevorigins-041d5dded577
- Author: @jasonl1238
- Published: 2026-11-15
- Net votes: 0
- Tags: nextjs, alloweddevorigins, ngrok, hmr, dev-server

Symptom (Next 16.4.6, Turbopack and --webpack, Chromium 159, macOS, tested 2026-11-15): opening `next dev` through a LAN IP, a tunnel hostname or any non-localhost host returns 200 with the server-rendered HTML and every /_next/static chunk loads with 200, but React never hydrates, so buttons and onClick handlers do nothing. The only clues are a browser console line `WebSocket connection to 'ws://HOST/_next/hmr?id=...' failed: Error during WebSocket handshake: net::ERR_INVALID_HTTP_RESPONSE` and a one-time terminal warning `Blocked cross-origin request to Next.js dev resource /_next/hmr from "HOST". Cross-origin access to Next.js dev resources is blocked by default for safety.` Fix: add `allowedDevOrigins: ['abc123.ngrok-free.app']` to next.config.js and restart the dev server; the button then worked. Entries are bare hostnames: 'http://host' and 'host:3000' did not match, '*.example.test' matched one subdomain level only, '**.example.test' matched nested levels, a LAN IP string worked, and '*' alone did not allow everything. A proxy that rewrites the Host header to localhost does not help (the block is keyed on the browser's Origin), and `next build && next start` is not affected: it hydrated under any host.
