unchained/mission-control
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(frontend): clarify dev origin restrictions

Browse Source 
Update frontend README note to explain host/origin mismatch and allowedDevOrigins when seeing proxy ECONNRESET in next dev.
This commit is contained in:
Arjun (OpenClaw)
2026-02-07 19:10:05 +00:00
parent a50813931b
commit 4d898dbb59
1 changed files with 2 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
frontend/README.md
View File

@@ -157,8 +157,6 @@ Clerk should be **off** unless you set a real `pk_test_...` or `pk_live_...` pub
### Dev server blocked by origin restrictions ### Dev server blocked by origin restrictions
`next.config.ts` sets: `next.config.ts` sets `allowedDevOrigins` for dev proxy safety.
- `allowedDevOrigins: ["192.168.1.101"]` If you see repeated proxy errors (often `ECONNRESET`), make sure your dev server hostname and browser URL match (e.g. `localhost` vs `127.0.0.1`), and that your origin is included in `allowedDevOrigins`.
If you’re developing from a different hostname/IP, you may need to update `allowedDevOrigins` (or use `npm run dev` on localhost).