Skip to content

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.

  1. Open Control Hub on your desktop to check the container logs for clawdbot.

    Check container logs

  2. Look for the following error message. If it appears, proceed to the next step.

    text
    Gateway 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

    Error logs

  3. Open Settings, go to Application > OpenClaw > Control UI > Set up endpoint, and then copy the endpoint address.

    OpenClaw endpoint address

  4. Open Files, go to Application > Data > clawdbot > config, right-click the openclaw.json file, and then download it.

    OpenClaw configuration file

  5. Open the downloaded file in a text editor, find the gateway section, and then add a controlUi block with your endpoint address.

    json
    "controlUi": {
      "allowedOrigins": ["Endpoint-Address"]
    },

    Update configuration file

    INFO

    If you access the Control UI using multiple addresses such as local URLs or custom domains, add them to the allowedOrigins array separated by commas. For example, ["https://url-one.com", "https://url-two.com"].

  6. Return to Files, rename the original openclaw.json file to keep it as a backup, and then upload your modified openclaw.json file.

  7. Return to Control Hub, click clawdbot under Deployments, and then click Restart in the upper-right corner.

    Restart OpenClaw

  8. In the Restart clawdbot window, type clawdbot exactly as shown, and then click Confirm. Wait for the program status to show as Running, which is indicated by a green dot.

    Restart finish

  9. Check the container logs again to verify the gateway has started successfully.

    Verify container logs

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