Asosiy tarkibga o'tish

​
Gateway service runbook

Last updated: 2025-12-09

Deep troubleshooting

Alomatlardan boshlanadigan diagnostika aniq buyruqlar ketma-ketligi va log imzolari bilan.

Configuration

Vazifaga yo‘naltirilgan o‘rnatish qo‘llanmasi + to‘liq konfiguratsiya ma’lumotnomasi.

​
5 daqiqalik lokal ishga tushirish

1

Start the Gateway

openclaw gateway --port 18789
# for full debug/trace logs in stdio:
openclaw gateway --port 18789 --verbose
# if the port is busy, terminate listeners then start:
openclaw gateway --force
# dev loop (auto-reload on TS changes):
pnpm gateway:watch
2

Verify service health

openclaw gateway status
openclaw status
openclaw logs --follow
Sog‘lom asosiy holat: Runtime: running va RPC probe: ok.
3

Validate channel readiness

openclaw channels status --probe
Gateway konfiguratsiyasini qayta yuklash faol konfiguratsiya fayli yo‘lini kuzatadi (profil/state sukut bo‘yicha qiymatlaridan aniqlanadi yoki OPENCLAW_CONFIG_PATH o‘rnatilgan bo‘lsa, o‘shandan olinadi). Sukut bo‘yicha rejim gateway.reload.mode="hybrid".

​
Runtime modeli

  • Marshrutlash, boshqaruv tekisligi va kanal ulanishlari uchun doimiy ishlaydigan bitta jarayon.
  • Quyidagilar uchun yagona multiplekslangan port:
    • WebSocket boshqaruvi/RPC
    • HTTP API’lar (OpenAI-mos, Responses, tools invoke)
    • Boshqaruv UI va hook’lar
  • Sukut bo‘yicha bind rejimi: loopback.
  • Sukut bo‘yicha autentifikatsiya talab qilinadi (gateway.auth.token / gateway.auth.password yoki OPENCLAW_GATEWAY_TOKEN / OPENCLAW_GATEWAY_PASSWORD).

​
Dev profili (--dev)

SozlamaAniqlash tartibi
Gateway porti--port → OPENCLAW_GATEWAY_PORT → gateway.port → 18789
Bind rejimiCLI/override → gateway.bind → loopback

​
Hot reload rejimlari

gateway.reload.modeXatti-harakat
offKonfiguratsiya qayta yuklanmaydi
hotFaqat hot uchun xavfsiz o‘zgarishlarni qo‘llash
restartQayta yuklash talab qilinadigan o‘zgarishlarda restart qilish
hybrid (sukut bo‘yicha)Xavfsiz bo‘lsa hot qo‘llash, zarur bo‘lsa restart qilish

​
Operator buyruqlari to‘plami

openclaw gateway status
openclaw gateway status --deep
openclaw gateway status --json
openclaw gateway install
openclaw gateway restart
openclaw gateway stop
openclaw logs --follow
openclaw doctor

​
Remote access

Tavsiya etiladi: Tailscale/VPN. Zaxira usul: SSH tunnel. 
ssh -N -L 18789:127.0.0.1:18789 user@host
Service install per profile:
Agar gateway auth sozlangan bo‘lsa, mijozlar hatto SSH tunnel orqali ham auth (token/password) yuborishi shart.
Qarang: Remote Gateway, Authentication, Tailscale.

​
Nazorat va xizmat hayotiy sikli

Ishlab chiqarish muhitiga yaqin ishonchlilik uchun supervised ishga tushirishdan foydalaning. 
openclaw gateway install
openclaw gateway status
openclaw gateway restart
openclaw gateway stop
LaunchAgent yorliqlari ai.openclaw.gateway (standart) yoki ai.openclaw.<profile> (nomlangan profil). openclaw doctor xizmat konfiguratsiyasidagi tafovutlarni tekshiradi va tuzatadi.

​
Bitta hostda bir nechta gateway

Ko‘pchilik sozlamalarda bitta Gateway ishga tushirilishi kerak. Bir nechta gateway’dan faqat qat’iy izolyatsiya/yaxlitlik (masalan, qutqaruv profili) uchun foydalaning. Checklist per instance:
  • Noyob gateway.port
  • Noyob OPENCLAW_CONFIG_PATH
  • Noyob OPENCLAW_STATE_DIR
  • Noyob agents.defaults.workspace
Example: 
OPENCLAW_CONFIG_PATH=~/.openclaw/a.json OPENCLAW_STATE_DIR=~/.openclaw-a openclaw gateway --port 19001
OPENCLAW_CONFIG_PATH=~/.openclaw/b.json OPENCLAW_STATE_DIR=~/.openclaw-b openclaw gateway --port 19002
Qarang: Multiple gateways.

​
Gateway service management (CLI)

openclaw --dev setup
openclaw --dev gateway --allow-unconfigured
openclaw --dev status
Standart sozlamalar izolyatsiyalangan state/config va asosiy gateway porti 19001 ni o‘z ichiga oladi.

​
Protocol bo‘yicha qisqa ma’lumot (operator ko‘rinishi)

  • gateway status probes the Gateway RPC by default using the service’s resolved port/config (override with --url).
  • gateway status --deep adds system-level scans (LaunchDaemons/system units).
  • gateway status --no-probe skips the RPC probe (useful when networking is down).
  • gateway status --json is stable for scripts.
Bundled mac app:
  1. Darhol qabul qilingan tasdiq (status:"accepted")
  2. To stop it cleanly, use openclaw gateway stop (or launchctl bootout gui/$UID/bot.molt.gateway).
To‘liq protocol hujjatlari: Gateway Protocol.

​
Operational checks

​
Liveness

  • WS oching va connect yuboring.
  • Snapshot bilan hello-ok javobini kuting.

​
Readiness

openclaw gateway status
openclaw channels status --probe
openclaw health

​
Uzilishdan tiklanish

Events are not replayed. Ketma-ketlikda uzilishlar bo‘lsa, davom etishdan oldin holatni yangilang (health, system-presence).

​
Keng tarqalgan nosozlik belgilari

BelgiEhtimoliy muammo
refusing to bind gateway ... without authLoopback bo‘lmagan bind token/passwordsiz
another gateway instance is already listening / EADDRINUSEPort ziddiyati
Gateway start blocked: set gateway.mode=localConfig remote rejimga o‘rnatilgan
ulanish vaqtida unauthorizedClient va gateway o‘rtasida autentifikatsiya mos kelmasligi
To‘liq diagnostika bosqichlari uchun Gateway Troubleshooting dan foydalaning.

​
Windows (WSL2)

  • Gateway protokoli clientlari Gateway mavjud bo‘lmaganda darhol xatolik qaytaradi (to‘g‘ridan-to‘g‘ri kanalga avtomatik o‘tish yo‘q).
  • Yaroqsiz/birinchi ulanishga tegishli bo‘lmagan freymlar rad etiladi va yopiladi.
  • Socket yopilishidan oldin muloyim yopilish shutdown hodisasini chiqaradi.
Bog‘liq: