Giving up Zeabur, OpenClaw Issue

Resolved

VVintageFREE2/25/2026

I'm new to Zeabur and deployed OpenClaw using the provided template. I can access the web interface successfully, but I'm running into an issue when trying to set up a cron job — OpenClaw responds with "gateway isn't paired".

I assumed the template deployment would handle the gateway pairing automatically without any extra steps. Could you help clarify what needs to be done?

Here is the output from openclaw gateway status for reference:
-----
我是 Zeabur 的新用戶，使用官方模板部署了 OpenClaw。Web 介面可以正常訪問，但每次我請 OpenClaw 設置定時任務（cron job）時，它都會回應 「gateway isn't paired（閘道器未配對）」。

我以為使用模板部署後，閘道器配對應該會自動完成，不需要額外手動設置。請問這是需要額外操作的步驟嗎？

以下是 openclaw gateway status 的輸出供參考：
---
gateway connect failed: Error: pairing required

Gateway: bind=loopback (127.0.0.1), port=18789
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: unknown (Error: systemctl --user unavailable: spawn systemctl ENOENT)
RPC probe: failed
gateway closed (1008): pairing required

systemd user services unavailable.
Port 18789 is already in use.

5 Replies

VVintageFREE2/25/2026


root@service---:/app# openclaw devices list

🦞 OpenClaw 2026.2.19 (unknown) — I'm not magic—I'm just extremely persistent with retries and coping strategies.

│
gateway connect failed: Error: pairing required
◇ 
[openclaw] CLI failed: Error: gateway closed (1008): pairing required
Gateway target: ws://127.0.0.1:18789
Source: local loopback
Config: /home/node/.openclaw/openclaw.json
Bind: loopback
 at Object.onClose (file:///app/dist/call-pduzpefz.js:439:10)
 at WebSocket.<anonymous> (file:///app/dist/client-hc4zXmLk.js:1538:23)
 at WebSocket.emit (node:events:519:28)
 at WebSocket.emitClose (/app/node_modules/.pnpm/[email protected]/node_modules/ws/lib/websocket.js:273:10)
 at Socket.socketOnClose (/app/node_modules/.pnpm/[email protected]/node_modules/ws/lib/websocket.js:1346:15)
 at Socket.emit (node:events:519:28)
 at TCP.<anonymous> (node:net:346:12)

why using command line always say pairing required?


root@service---:/app# openclaw gateway status

🦞 OpenClaw 2026.2.19 (unknown) — One CLI to rule them all, and one more restart because you changed the port.

│
gateway connect failed: Error: pairing required
◇ 
Service: systemd (disabled)
File logs: /tmp/openclaw/openclaw-2026-02-25.log

Service config looks out of date or non-standard.
Service config issue: Gateway service PATH is not set; the daemon should use a minimal PATH.
Recommendation: run "openclaw doctor" (or "openclaw doctor --repair").
Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json

Gateway: bind=loopback (127.0.0.1), port=18789 (env/config)
Probe target: ws://127.0.0.1:18789
Dashboard: http://127.0.0.1:18789/
Probe note: Loopback-only gateway; only local clients can connect.

Runtime: unknown (Error: systemctl --user unavailable: spawn systemctl ENOENT)
RPC probe: failed
RPC target: ws://127.0.0.1:18789
 gateway closed (1008): pairing required
 Gateway target: ws://127.0.0.1:18789
 Source: cli --url
 Config: /home/node/.openclaw/openclaw.json

systemd user services unavailable.
systemd user services are unavailable; install/enable systemd or run the gateway under your supervisor.
If you're in a container, run the gateway in the foreground instead of `openclaw gateway`.

Port 18789 is already in use.
- Port is in use but process details are unavailable (install lsof or run as an admin user).
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting

CCanEMPLOYEE2/26/2026

Hey! Just to confirm — after deploying the template, did you run any extra steps (e.g. openclaw onboard / openclaw doctor / gateway restart), or change any env vars / config?

VVintageFREE2/27/2026

original i didnt run any steps, and then webpage can connect to gateway
i wanna know in zeabur offer
can we run openclaw onboard / openclaw doctor / gateway restart?

CCanEMPLOYEE2/28/2026

Yep — on Zeabur you can run most OpenClaw commands in the terminal, but a few of them behave differently because it’s a container environment.

- openclaw doctor: ✅ OK to run. It only checks configs / connectivity and is safe.

- openclaw onboard: ⚠️ Not recommended on Zeabur template. The template is already pre-configured, and running onboard may overwrite gateway/provider settings.

- openclaw gateway restart: ❌ Usually won’t work inside the container because it relies on systemd systemctl --user), which isn’t available.

If you need to “restart gateway” on Zeabur, just restart the service from the Zeabur dashboard.

Also make sure OPENCLAW_GATEWAY_BIND=lan in Zeabur, otherwise the gateway may not be reachable from other services.

AAnonymous3/4/2026

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

This issue has been marked as resolved

New replies are disabled for resolved issues.

Forum

5 Replies