2026-03-01T22-56-23_auto_memory/memories.db-wal, memory/memories.db, memory
This commit is contained in:
parent
1d352f83f8
commit
8f51789188
15
memory/2026-03-01-openclaw-gateway-crash-loop-fix.md
Normal file
15
memory/2026-03-01-openclaw-gateway-crash-loop-fix.md
Normal file
@ -0,0 +1,15 @@
|
||||
# 2026-03-01 Session Notes
|
||||
|
||||
## OpenClaw Gateway Crash Loop Fix
|
||||
|
||||
Fixed OpenClaw gateway crash loop caused by missing `controlUi.allowedOrigins` configuration. The gateway was set to `bind: "lan"` which added a Tailscale interface (100.119.174.58) as a non-loopback address, triggering OpenClaw's security check that requires explicit origin allowlisting for non-loopback Control UI access.
|
||||
|
||||
Error: `non-loopback Control UI requires gateway.controlUi.allowedOrigins (set explicit origins), or set gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback=true`
|
||||
|
||||
Implemented fix by editing `/home/nicholai/.openclaw/openclaw.json` to add `controlUi` section with `allowedOrigins` array containing:
|
||||
- Loopback addresses: `http://localhost:18789`, `http://127.0.0.1:18789`
|
||||
- Local network: `http://10.0.0.189:18789`
|
||||
- Tailscale interface: `http://100.119.174.58:18789`
|
||||
- Hostname: `http://archlinux:18789`
|
||||
|
||||
The `controlUi` block was inserted between `auth` and `tailscale` sections within the `gateway` config object. Service restart verified via `systemctl --user restart openclaw-gateway.service` with status and journal log inspection.
|
||||
Binary file not shown.
Binary file not shown.
Binary file not shown.
Loading…
x
Reference in New Issue
Block a user