Gateway Error | Friends of the Crustacean 🦞🤝 | Page 1

viral forge Apr 27, 2026, 6:45 AM

#

openclaw gateway error

visual tinselBOT Apr 27, 2026, 6:45 AM

#

To help others find answers, you can mark your question as solved via Right click solution message -> Apps -> ✅ Mark Solution

stoic orioleBOT Apr 27, 2026, 6:46 AM

#

Can you paste the exact error + version first?

Run these read-only checks:

openclaw --version
openclaw status --all
openclaw gateway status

If the gateway won’t start / RPC is down, also paste the latest log tail:

openclaw logs --tail 80

or, if that fails:

#

tail -80 "$(ls -t /tmp/openclaw/openclaw-*.log | head -1)"

status --all should redact tokens, but still skim before posting. Gateway troubleshooting docs are here: https://docs.openclaw.ai/gateway/troubleshooting 🦐

viral forge Apr 27, 2026, 6:48 AM

#

coba cek status openclaw berikut

Agents
┌───────────────────────────────┬────────────────┬──────────┬──────────┬───────────────────────────────────────────────┐
│ Agent                         │ Bootstrap file │ Sessions │ Active   │ Store                                         │
├───────────────────────────────┼────────────────┼──────────┼──────────┼───────────────────────────────────────────────┤
│ main                          │ ABSENT         │       32 │ 38m ago  │ ~/.openclaw/agents/main/sessions/sessions.    │
│                               │                │          │          │ json                                          │
│ produktivitas (produktivitas) │ PRESENT        │        0 │ unknown  │ ~/.openclaw/agents/produktivitas/sessions/    │
│                               │                │          │          │ sessions.json                                 │
│ skripsi (skripsi)             │ PRESENT        │        0 │ unknown  │ ~/.openclaw/agents/skripsi/sessions/sessions. │
│                               │                │          │          │ json                                          │
└───────────────────────────────┴────────────────┴──────────┴──────────┴───────────────────────────────────────────────┘

Diagnosis (read-only)

Gateway connection details:
  Gateway target: ws://127.0.0.1:18789
  Source: local loopback
  Config: /root/.openclaw/openclaw.json
  Bind: lan

✓ Config: /root/.openclaw/openclaw.json
✓ Secret diagnostics (0)
✓ Restart sentinel: none
! Port 18789
  Port 18789 is already in use.
  - pid 442 root: openclaw-gateway (*:18789)
  - Gateway already running locally. Stop it (openclaw gateway stop) or use a different port.
! Tailscale: off · unknown
✓ Skills: 15 eligible · 0 missing · /root/.openclaw/workspace/main
✓ Plugin compatibility (none)

Gateway restart attempts (tail): /root/.openclaw/logs/gateway-restart.log
  [2026-04-26T12:07:32Z] openclaw restart attempt source=update target=openclaw-gateway.service
  [2026-04-26T12:07:32Z] openclaw restart done source=update
! Channel issues skipped (gateway unreachable)

Gateway health:
  timeout

Pasteable debug report. Auth tokens redacted.
Troubleshooting: https://docs.openclaw.ai/troubleshooting

stoic orioleBOT Apr 27, 2026, 6:49 AM

#

Kelihatannya gateway process-nya hidup tapi nge-hang / tidak responsif.

Yang penting dari status itu:

pid 442 root: openclaw-gateway (*:18789) → port dipakai oleh OpenClaw gateway sendiri, bukan app lain.
Gateway health: timeout + Channel issues skipped (gateway unreachable) → CLI bisa lihat prosesnya, tapi gateway tidak menjawab health probe.
Bootstrap file PRESENT di agent produktivitas / skripsi kemungkinan bukan penyebab gateway timeout; itu baru relevan kalau agent stuck saat sesi mulai.

Coba ini dulu:

openclaw --version
openclaw gateway status --deep
openclaw logs --tail 120
openclaw gateway restart
sleep 5

#

openclaw status --all
openclaw health --verbose

Kalau masih timeout setelah restart, paste output dari:

openclaw logs --tail 200
journalctl -u openclaw-gateway -n 200 --no-pager

Kalau journalctl -u kosong, coba:

journalctl --user -u openclaw-gateway -n 200 --no-pager

#

Untuk sekarang jangan ganti port dulu — ini lebih terlihat seperti gateway-nya stuck, bukan konflik port beneran. Docs troubleshooting: https://docs.openclaw.ai/gateway/troubleshooting 🦐

viral forge Apr 27, 2026, 6:51 AM

#

cek

openclaw gateway status --deep

🦞 OpenClaw 2026.4.24 (cbcfdf6) — If you can describe it, I can probably automate it—or at least make it funnier.

│
◇
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-27.log
Command: /usr/bin/node /usr/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json

Gateway: bind=lan (0.0.0.0), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://10.206.15.106:18789/
Probe note: bind=lan listens on 0.0.0.0 (all interfaces); probing via 127.0.0.1.

Runtime: stopped (state activating, sub auto-restart, last exit 1, reason 1)
Connectivity probe: failed
Probe target: ws://127.0.0.1:18789
  connect ECONNREFUSED 127.0.0.1:18789
Capability: unknown

Service is loaded but not running (likely exited immediately).
File logs: /tmp/openclaw/openclaw-2026-04-27.log
Logs: journalctl --user -u openclaw-gateway.service -n 200 --no-pager
Restart attempts: /root/.openclaw/logs/gateway-restart.log

Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting

stoic orioleBOT Apr 27, 2026, 6:51 AM

#

Ini sudah lebih jelas: gateway service-nya crash saat startup.

Artinya:

last exit 1 → proses gateway keluar dengan error.
state activating, sub auto-restart → systemd terus coba restart.
ECONNREFUSED → saat dicek, gateway belum berhasil listen di port 18789.

Sekarang yang dibutuhkan adalah error asli dari log. Paste output ini:

openclaw logs --tail 200
journalctl --user -u openclaw-gateway.service -n 200 --no-pager

Kalau output log ada error seperti ENOTEMPTY, plugin-runtime-deps, atau dependency install gagal, kemungkinan ini kena regression di 2026.4.24. Tapi jangan rollback dulu sebelum lihat lognya.

Docs: https://docs.openclaw.ai/gateway/troubleshooting 🦐

viral forge Apr 27, 2026, 6:53 AM

#

cek

Apr 27 06:51:48 openclaw-box node[969]: 2026-04-27T06:51:48.117+00:00 [gateway] ⚠️  Gateway is binding to a non-loopback address. Ensure authentication is configured before exposing to public networks.
Apr 27 06:51:48 openclaw-box node[969]: 2026-04-27T06:51:48.248+00:00 [health-monitor] started (interval: 300s, startup-grace: 60s, channel-connect-grace: 120s)
Apr 27 06:51:48 openclaw-box node[969]: 2026-04-27T06:51:48.956+00:00 [gateway] agent model: openai-codex/gpt-5.4
Apr 27 06:51:48 openclaw-box node[969]: 2026-04-27T06:51:48.959+00:00 [gateway] ready (8 plugins: acpx, bonjour, browser, device-pair, discord, memory-core, phone-control, talk-voice; 10.7s)
Apr 27 06:51:48 openclaw-box node[969]: 2026-04-27T06:51:48.961+00:00 [gateway] log file: /tmp/openclaw/openclaw-2026-04-27.log
Apr 27 06:51:48 openclaw-box node[969]: 2026-04-27T06:51:48.966+00:00 [gateway] security warning: dangerous config flags enabled: gateway.controlUi.allowInsecureAuth=true. Run `openclaw security audit`.
Apr 27 06:51:48 openclaw-box node[969]: 2026-04-27T06:51:48.986+00:00 [gateway] starting channels and sidecars...
Apr 27 06:51:49 openclaw-box node[969]: 2026-04-27T06:51:49.596+00:00 [hooks] loaded 4 internal hook handlers
Apr 27 06:51:59 openclaw-box node[969]: 2026-04-27T06:51:59.107+00:00 [plugins] bonjour: watchdog detected non-announced service; attempting re-advertise (gateway fqdn=openclaw-box._openclaw-gw._tcp.local. host=openclaw.local. port=18789 state=probing)
Apr 27 06:52:16 openclaw-box node[969]: 2026-04-27T06:52:16.227+00:00 [plugins] bonjour: restarting advertiser (service stuck in probing for 17121ms (gateway fqdn=openclaw-box._openclaw-gw._tcp.local. host=openclaw.local. port=18789 state=probing))
Apr 27 06:52:16 openclaw-box node[969]: 2026-04-27T06:52:16.241+00:00 [plugins] bonjour: advertised gateway fqdn=openclaw-box._openclaw-gw._tcp.local. host=openclaw.local. port=18789 state=unannounced
Apr 27 06:52:16 openclaw-box node[969]: 2026-04-27T06:52:16.243+00:00 [openclaw] Unhandled promise rejection: CIAO PROBING CANCELLED
Apr 27 06:52:16 openclaw-box node[969]: 2026-04-27T06:52:16.250+00:00 [openclaw] wrote stability bundle: /root/.openclaw/logs/stability/openclaw-stability-2026-04-27T06-52-16-247Z-969-unhandled_rejection.json
Apr 27 06:52:16 openclaw-box systemd[409]: openclaw-gateway.service: Main process exited, code=exited, status=1/FAILURE
Apr 27 06:52:16 openclaw-box systemd[409]: openclaw-gateway.service: Failed with result 'exit-code'.
Apr 27 06:52:16 openclaw-box systemd[409]: openclaw-gateway.service: Consumed 45.863s CPU time.
Apr 27 06:52:21 openclaw-box systemd[409]: openclaw-gateway.service: Scheduled restart job, restart counter is at 12.
Apr 27 06:52:21 openclaw-box systemd[409]: Started openclaw-gateway.service - OpenClaw Gateway (v2026.4.24).

stoic orioleBOT Apr 27, 2026, 6:53 AM

#

Yep, ketemu penyebabnya: Bonjour/mDNS plugin crash.

Baris kuncinya:

[plugins] bonjour: restarting advertiser ...
[openclaw] Unhandled promise rejection: CIAO PROBING CANCELLED
Main process exited, status=1/FAILURE

Gateway sebenarnya sempat ready, lalu mati karena Bonjour advertiser stuck di probing.

Coba workaround paling cepat:

openclaw gateway stop

#

openclaw plugins disable bonjour
openclaw gateway restart
sleep 5
openclaw gateway status --deep

Kalau sudah jalan, test:

openclaw health --verbose
openclaw status --all

Ini cuma mematikan LAN auto-discovery / Bonjour, bukan mematikan gateway. Kamu masih bisa akses langsung lewat URL/IP gateway.

Kalau masih crash, paste juga stability bundle ini:

#

cat /root/.openclaw/logs/stability/openclaw-stability-2026-04-27T06-52-16-247Z-969-unhandled_rejection.json

Dan karena ini di 2026.4.24, kemungkinan bug/regression — bagus juga dibuat GitHub issue dengan log CIAO PROBING CANCELLED: https://github.com/openclaw/openclaw/issues 🦐

viral forge Apr 27, 2026, 6:55 AM

#

fungsi bonjour buat apa?

stoic orioleBOT Apr 27, 2026, 6:55 AM

#

Bonjour itu untuk auto-discovery di LAN.

Fungsinya: perangkat lain di jaringan lokal bisa “menemukan” gateway OpenClaw otomatis, misalnya mobile/node/control UI melihat gateway tanpa kamu ketik IP manual.

Kalau Bonjour dimatikan:

✅ Gateway tetap jalan
✅ Discord/agent/tool tetap bisa jalan
✅ Dashboard tetap bisa dibuka pakai URL/IP langsung, misalnya http://10.206.15.106:18789/
❌ Perangkat lain mungkin tidak otomatis menemukan gateway
❌ Kamu perlu connect manual pakai IP / Tailscale / SSH tunnel / URL langsung

Jadi untuk kasus kamu, aman dimatikan dulu karena yang crash cuma fitur discovery-nya, bukan core gateway. Docs: https://docs.openclaw.ai/gateway/bonjour 🦐

viral forge Apr 27, 2026, 6:57 AM

#

okee sip coba cek

openclaw gateway status --deep

🦞 OpenClaw 2026.4.24 (cbcfdf6) — Say "stop" and I'll stop—say "ship" and we'll both learn a lesson.

│
◇
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-04-27.log
Command: /usr/bin/node /usr/lib/node_modules/openclaw/dist/index.js gateway --port 18789
Service file: ~/.config/systemd/user/openclaw-gateway.service
Service env: OPENCLAW_GATEWAY_PORT=18789

Config (cli): ~/.openclaw/openclaw.json
Config (service): ~/.openclaw/openclaw.json

Gateway: bind=lan (0.0.0.0), port=18789 (service args)
Probe target: ws://127.0.0.1:18789
Dashboard: http://10.206.15.106:18789/
Probe note: bind=lan listens on 0.0.0.0 (all interfaces); probing via 127.0.0.1.

Runtime: running (pid 1156, state active, sub running, last exit 0, reason 0)
Connectivity probe: ok
Capability: admin-capable

Listening: *:18789
Troubles: run openclaw status
Troubleshooting: https://docs.openclaw.ai/troubleshooting

stoic orioleBOT Apr 27, 2026, 6:57 AM

#

Mantap, itu sudah sehat ✅

Yang penting:

Runtime: running
Connectivity probe: ok
Capability: admin-capable
Listening: *:18789

Berarti gateway sudah jalan normal setelah Bonjour dimatikan.

Final check opsional:

#

openclaw health --verbose
openclaw status --all

Kalau semua oke, problemnya memang Bonjour/mDNS crash di 2026.4.24. Kalau ini sudah fix, boleh Mark Solution biar ke-index di Answer Overflow:

right-click pesan solusi → Apps → ✅ Mark Solution 🦐

#Gateway Error