Upgrade OpenClaw
Before upgrading an existing OpenClaw installation, review the version-specific changes and troubleshooting steps on this page to ensure a smooth transition.
Upgrade to 2026.02.25
The OpenClaw 2026.02.25 update introduced a security enhancement that requires existing users to explicitly declare the allowed Control UI access address. Therefore, if your Control UI fails to start after the upgrade, follow these steps to resolve the issue.
Open Control Hub on your desktop to check the container logs for clawdbot.

Look for the following error message. If it appears, proceed to the next step.
textGateway failed to start: Error: non-loopback Control UI requires gateway.controlUi.allowedOrigins (set explicit origins), or set gateway.controlUi.dangerouslyAllowHostHeaderOriginFallback=true to use Host-header origin fallback mode
Open Settings, go to Application > OpenClaw > Control UI > Set up endpoint, and then copy the endpoint address.

Open Files, go to Application > Data > clawdbot > config, right-click the
openclaw.jsonfile, and then download it.
Open the downloaded file in a text editor, find the
gatewaysection, and then add acontrolUiblock with your endpoint address.json"controlUi": { "allowedOrigins": ["Endpoint-Address"] },
INFO
If you access the Control UI using multiple addresses such as local URLs or custom domains, add them to the
allowedOriginsarray separated by commas. For example,["https://url-one.com", "https://url-two.com"].Return to Files, rename the original
openclaw.jsonfile to keep it as a backup, and then upload your modifiedopenclaw.jsonfile.Return to Control Hub, click clawdbot under Deployments, and then click Restart in the upper-right corner.

In the Restart clawdbot window, type
clawdbotexactly as shown, and then click Confirm. Wait for the program status to show as Running, which is indicated by a green dot.
Check the container logs again to verify the gateway has started successfully.

Open the Control UI. Refresh the browser page if an error still displays.