Updated manually the image to 2026.3.28 - Gateway is not reachable over the subdomain and the public internet anymore

Author: alnevenCreated Mar 31, 2026Updated Sep 1, 2026

hi @andrasbacsai

after I manually updated the docker image to the latest stable, 2026.3.28 I'm receiving this under the subdomain of my openclaw bot: origin not allowed (open the Control UI from the gateway host or allow it in gateway.controlUi.allowedOrigins)

when I search for a solution, I get different ideas like these: origin not allowed

By default, it only allows:

localhost the gateway host itself Add allowed origins

Update or add: gateway: controlUi: allowedOrigins: - "https://your-subdomain.example.com"

or In your Coolify app:

Go to Environment Variables Add something like: GATEWAY_CONTROLUI_ALLOWEDORIGINS=https://a.example.com,https://b.example.com,http://a.example.com

Then redeploy

somehow if I do this, or manually change the /data/.openclaw/openclaw.json nothing happens, it is not a fix which works...

any idea?

summary: To fix OpenClaw "origin not allowed" errors, configure gateway.controlUi.allowedOrigins in ~/.openclaw/openclaw.json with your exact browser URL (e.g., ["http://localhost:18789"]). Use exact origins instead of *. For Docker/remote, use http://:18789. Restart the gateway after changes. For Coolify, use env. vars.