Troubleshooting

“Origin Not Allowed” in Control UI

Fix the error that blocks dashboard access after a restart, URL change, or moving from local to VPS.

⏱ About 4 minutes
What this means

The dashboard URL you're opening is not in your gateway's allowed origin list. The gateway is rejecting the browser for safety.

Fast Fix (Do These In Order)

1

Copy the exact origin from your browser

Grab only protocol + host + port (for example: https://my-agent.example.com or http://192.168.1.10:3010).

Common gotcha

A trailing slash or wrong port can make it fail. Origins must match exactly.

2

Add that origin to gateway.controlUi.allowedOrigins

In your gateway config, add the exact origin to the allow-list and save.

{ "gateway": { "controlUi": { "allowedOrigins": [ "https://my-agent.example.com", "http://192.168.1.10:3010" ] } } }
3

Restart the gateway once

Apply config changes with a clean restart, then wait 20-30 seconds.

openclaw gateway restart
4

Retest in one clean browser tab

Close duplicate tabs, open one tab to the same URL, and test again. If needed, hard refresh once.

Success check

Control UI loads without the origin error and you can run a basic command.


High-Friction Edge Cases

Worked yesterday, broken today after moving to VPS

You likely still have a local origin allowed, but not the new VPS domain. Add the VPS origin explicitly and restart.

HTTPS URL in browser, HTTP origin in config

Scheme mismatch is a hard fail. https:// and http:// are different origins.

One teammate can load it, another cannot

They may be using different URLs (domain vs IP, or different ports). Add each legitimate origin you actually use.


When to Escalate to #help

If it still fails, post this evidence so support can help quickly: