Openclaw Error

Pending author confirmation

POPeters OwenDEVELOPER10h ago

Issue Summary:

Service Name: OpenClaw
Service ID: 699444ad5e4cca5b2f14fb1c
Project ID: 6994443a5e4cca5b2f14fae2
Environment ID: 6994443a0568457b6d44925b
Status: CRASHED
Error Message:

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

What I've Tried:

Added environment variables: GATEWAY_CONTROL_UI_ALLOWED_ORIGINS=* and GATEWAY_CONTROL_UI_DANGEROUSLY_ALLOW_HOST_HEADER_ORIGIN_FALLBACK=true
Updated to OpenClaw-specific naming: OPENCLAW_GATEWAY_CONTROL_UI_ALLOWED_ORIGINS and OPENCLAW_GATEWAY_CONTROL_UI_DANGEROUSLY_ALLOW_HOST_HEADER_ORIGIN_FALLBACK
Service continues to crash with the same gateway configuration error
The support team should be able to provide the correct configuration format for OpenClaw on Zeabur or help troubleshoot this specific issue.

2 Replies

CCanEMPLOYEE9h ago

Hi,

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.

CCanEMPLOYEE9h ago

In your case add setup in gateway.contronUi

there are two options:

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

Add a Reply

Forum

2 Replies