Forum

The server keeps showing the error message in the attached image.

Solved the LLM model issue, but it's still stuck here.

The server won't start, so I've paused the service for now. Could you please help me check why it's failing to update the version?

Hello, I have confirmed the cause from the server side:

OpenClaw itself started normally (you can see gateway ready, http server listening in the logs, and the model openai-codex/gpt-5.4 was loaded successfully), so your previous direction of fixing the model was correct.

The real issue: The gateway.mode in the OpenClaw configuration file /home/node/.openclaw/openclaw.json is set to "local". This mode only binds the service to the container's internal loopback (127.0.0.1), but Zeabur's health check attempts to connect to port 18789 via the container's external IP, resulting in a "connection refused" error. The service gets stuck in the startup check and never reaches the RUNNING state, causing it to restart repeatedly. The "Tool result is missing" error that appeared during the AI upgrade is also due to this—the AI was waiting for the service to become RUNNING, but the health check timed out. Your data is not corrupted.

One additional note: Although you have set the environment variable OPENCLAW_GATEWAY_BIND=lan, the explicit gateway.mode: "local" in the configuration file overrides the environment variable, which is why it didn't take effect. You need to modify the configuration file itself.

Steps to modify:

1. Go to the service "Settings" and temporarily disable "Health Check" and save (to prevent the container from restarting due to failed checks while you are editing the file).
2. Restart the service and wait for the container to run.
3. Go to the "Files" tab, open /home/node/.openclaw/openclaw.json, and find the gateway block:

"gateway": {
 "mode": "local",
 "controlUi": { "allowInsecureAuth": true }
}

Change "mode": "local" to "mode": "lan" and save. 4. Return to "Settings", re-enable "Health Check", and then "Restart" the service.

After changing it to lan, OpenClaw will bind to the external interface, and once the health check passes, it will be online normally.

Additionally, I recommend pinning the image version from latest to a specific version number (e.g., 2026.5.28) to avoid unexpected changes when the service restarts and pulls a new version.

After making the changes and restarting the service, the error shown in the attachment appeared.

I used AI to check the issue, and it said I cannot change it to run on LAN.

And now, even after a restart, I can't even modify the files.

Following up, I made the following changes as instructed by Zeabur, but the server still won't start.

When submitting, please provide the following information:

• Service ID: 6981fc0326acd45e43c8692e
• Environment ID: 6981f56886311f632dc29cb0
• Project ID: 6981f568f9d3bc4cce7d30f6
• Error Message: Gateway start blocked: set gateway.mode=local (current: lan) or pass --allow-unconfigured
• Attempted Solutions:
• Changed OPENCLAW_GATEWAY_BIND from lan to local
• Added OPENCLAW_ALLOW_UNCONFIGURED=1

I have fixed it for you, and the service is now running normally (Running, public URL is working). Your data is intact, and features like LINE and scheduling remain unaffected.

【Reason (My apologies)】 The issue was caused by my previous incorrect suggestion. gateway.mode only accepts local or remote; my previous instruction to change it to lan was an invalid value, which caused the service to get stuck at "Gateway start blocked." This was unrelated to the version upgrade.

【What I did on the server side (Only modified the gateway block in openclaw.json; nothing else was touched, and backups of the original file were made)】

1. Changed gateway.mode back to the valid value local.
2. Added gateway.bind: "lan" — This allows the service to bind to the public interface so it can pass health checks and be accessed externally.
3. Added your domain to gateway.controlUi.allowedOrigins — This resolved the "Browser origin not allowed" error.

The service is now fully functional. The following steps are only required if you wish to use the built-in web management interface (Control UI):

【(Optional) Two prerequisites for opening the Control UI】

1. Access the URL with a token: https://stisopenclaw.zeabur.app?token=<your token> The token is your service's OPENCLAW_GATEWAY_TOKEN / PASSWORD environment variable, which can be found in Dashboard → Service → Variables.
2. For every new browser, you must perform a one-time device approval. Go to Dashboard → Service → Terminal and run: openclaw devices approve a2fcd752-6660-4928-8942-24a4bcf34bc6 (If you refresh or switch browsers, the ID will change. Run openclaw devices list first and use the one marked as "Pending".) After approval, refresh the Control UI tab.

If you encounter any further issues, please reply to this thread and I will take a look.

Thanks a lot! I can use the Control UI now.

Great, it would be perfect if you can access the Control UI. Enjoy using it!