Skip to content

fix: allow LAN access to the dev server - #532

Open
epheien wants to merge 1 commit into
agegr:mainfrom
epheien:fix/lan-access
Open

fix: allow LAN access to the dev server#532
epheien wants to merge 1 commit into
agegr:mainfrom
epheien:fix/lan-access

Conversation

@epheien

@epheien epheien commented Aug 17, 2026

Copy link
Copy Markdown

Problem

Next 16 blocks cross-origin access to dev resources by default. The previous allowedDevOrigins only covered 127.0.0.1 and 192.168.*.*, so visiting the dev server from a 10.x LAN address (e.g. 10.9.8.12) returned 403 on every /_next chunk and the HMR websocket failed, making the app unusable from other machines on the same LAN.

Fix

Allow the loopback and all RFC1918 private ranges used by the dev server:

  • 127.0.0.1
  • 10.0.0.0/8
  • 172.16.0.0/12
  • 192.168.0.0/16

Notes

  • Config-only change, no runtime behavior impact in production builds (allowedDevOrigins is dev-only).
  • Verified with npm run dev accessed from a 10.x LAN address: chunks and HMR websocket load correctly (eslint clean).

Next 16 blocks cross-origin access to dev resources by default; the old
allowedDevOrigins only covered 127.0.0.1 and 192.168.*.*, so visiting the
dev server from a 10.x LAN address returned 403 on every /_next chunk and
the HMR websocket. Allow loopback and the RFC1918 LAN ranges (10/8,
172.16/12, 192.168/16) so the dev server stays reachable from other
machines on the same LAN.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant