Forum

Add to config files should be ok

After upgrading to 2026.2.23 and later, you may 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.

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.

I did it with instruction above

Now your openclaw is working so you can follow setup guide to connect
https://zeabur.com/templates/ZBVZNH

I had try but still crash. Can you please check? 你的專案 OpenClaw 中的服務 openclaw-devbox 有一個部署崩潰了。

1. 建議你前往 Zeabur 官方論壇報告這個問題：https://zeabur.com/forum
   在論壇上提供以下信息會很有幫助：

• 服務 ID: 69a016eece2815de54592c43
• 錯誤信息: "pairing required"
• Gateway 服務 ID: service-69952ad246ce828f10f132a0 無法連接
  技術支持團隊可以幫助你診斷 Gateway 服務的問題。

ok, start up command is missing

Then enter command like this
openclaw devices list

openclaw devices approve <requestID>

I fixed for you this time.

thats great! thanks so much!

請訪問 Zeabur 官方論壇：https://zeabur.com/forum
在論壇上，你可以：

描述你遇到的問題（Gateway 無法啟動的錯誤）
提供以下信息給技術支持團隊：
服務名稱：OpenClaw-allic
服務 ID：69952ad246ce828f10f132a0
環境 ID：699188d80568457b6d447fb2
域名：dealerdon.zeabur.app
錯誤信息：Gateway failed to start: Error: non-loopback Control UI requires gateway.controlUi.allowedOrigins
附上我提供的日誌信息，這樣技術支持團隊可以更快地診斷問題
Zeabur 的技術支持團隊對於這類配置問題有豐富的經驗，他們應該能夠幫助你快速解決這個問題。

okay now. While I install the new skill, no idea it change "dangerouslyAllowHostHeaderOriginFallback": to false . Now I set to true by luck. Okay now.