Forum

Please follow the steps below to fix the config file error:

1. Go to Settings and change the start command to sleep 3600

2. Disable the health check.

3. Restart the service — the container will stay running, but OpenClaw will not start.

4. Check the logs to find the root cause of the error.

5. Open the Files tab and edit the config file (/home/node/.openclaw/openclaw.json). Remove the parameter(s) that are causing the error.

6. Change the start command back to /opt/openclaw/startup.sh && /opt/openclaw/start_gateway.sh

7. Restart the service again.

After upgrade 2026.2.23 or higher , you need to adjust the config based on the log hints. There are two options:

1. Enable fallback (less strict)
   "dangerouslyAllowHostHeaderOriginFallback": true
2. Whitelist your domain (recommended)
   "allowedOrigins": ["https://<your-app>.zeabur.app/"]

Once updated, restart the gateway and it should work.


for example

{
 "gateway": {
 "port": 18789,
 "controlUi": {
 "dangerouslyAllowHostHeaderOriginFallback": true,
 "allowInsecureAuth": true,
 "dangerouslyDisableDeviceAuth": true
 },
 }
}

This post has been inactive for a while. We will be closing it in 2 days if there is no new activity.