​

Gateway nosozliklarini bartaraf etish

​

Buyruqlar ketma-ketligi

openclaw status
openclaw gateway status
openclaw logs --follow
openclaw doctor
openclaw channels status --probe

• openclaw gateway status Runtime: running va RPC probe: ok holatini koʻrsatadi.
• openclaw doctor konfiguratsiya/xizmat bilan bogʻliq toʻsib qoʻyuvchi muammolar yoʻqligini bildiradi.
• openclaw channels status --probe ulangan/tayyor kanallarni koʻrsatadi.

​

No replies

openclaw status
openclaw channels status --probe
openclaw pairing list <channel>
openclaw config get channels
openclaw logs --follow

• 1. DM yuboruvchilar uchun juftlash kutilmoqda.
• 2. Guruh eslatmasini cheklash (requireMention, mentionPatterns).
• 3. Kanal/guruh ruxsat ro‘yxati nomuvofiqliklari.

4. Keng tarqalgan belgilar:

• 5. drop guild message (mention required → eslatma bo‘lmaguncha guruh xabari e’tiborsiz qoldiriladi.
• 6. pairing request → yuboruvchi tasdiqlanishi kerak.
• 7. blocked / allowlist → yuboruvchi/kanal siyosat bo‘yicha filtrlangan.

8. Bog‘liq:

• /channels/troubleshooting
• /channels/pairing
• /channels/groups

​

12. Boshqaruv paneli boshqaruv UI ulanishi

13. Boshqaruv paneli/boshqaruv UI ulanmasa, URL, autentifikatsiya rejimi va xavfsiz kontekst taxminlarini tekshiring.

14. openclaw shlyuzi holati

• openclaw logs —follow
• openclaw doctor
• openclaw gateway status —json

15. Qidiring:

• 16. To‘g‘ri probe URL va boshqaruv paneli URL.
• 17. Mijoz va shlyuz o‘rtasida autentifikatsiya rejimi/token nomuvofiqligi.
• 18. Qurilma identifikatori talab qilinadigan joyda HTTP’dan foydalanish.

19. Keng tarqalgan belgilar:

• /web/control-ui
• /gateway/authentication
• /gateway/remote

​

23. Bog‘liq:

24. /web/control-ui

25. [/gateway/authentication](/gateway/authentication)

• 27. Shlyuz xizmati ishga tushmagan
• 28. Xizmat o‘rnatilgan, lekin jarayon ishlashda qolmasa, shundan foydalaning.
• openclaw gateway status

• Gateway start blocked: set gateway.mode=local → local gateway rejimi yoqilmagan. Tuzatish: konfiguratsiyangizda gateway.mode="local" ni o‘rnating (yoki openclaw configure ni ishga tushiring). Agar OpenClaw’ni maxsus openclaw foydalanuvchisi orqali Podman bilan ishga tushirayotgan bo‘lsangiz, konfiguratsiya ~openclaw/.openclaw/openclaw.json manzilida joylashgan.
• openclaw doctor openclaw gateway status —deep
• 30. Qidiring:

31. Runtime: stopped va chiqish bo‘yicha maslahatlar.

• /gateway/background-process
• /gateway/configuration
• /gateway/doctor

​

35. Gateway start blocked: set gateway.mode=local → lokal shlyuz rejimi yoqilmagan.

36. `refusing to bind gateway …

37. without auth` → token/parolsiz loopback bo‘lmagan bind.

• 39. Bog‘liq:
• 40. /gateway/background-process
• 41. /gateway/configuration

42. /gateway/doctor

• mention required → guruh eslatish siyosati sababli xabar e’tiborsiz qoldiriladi.
• pairing / tasdiqlash kutilayotgan izlar → yuboruvchi tasdiqlanmagan.
• missing_scope, not_in_channel, Forbidden, 401/403 → kanal autentifikatsiyasi/ruxsatlari muammosi.

• /channels/troubleshooting
• /channels/whatsapp
• /channels/telegram
• /channels/discord

​

Cron va heartbeat yetkazib berilishi

openclaw cron holati
openclaw cron list
openclaw cron runs --id <jobId> --limit 20
openclaw system heartbeat last
openclaw logs --follow

• Cron yoqilgan va keyingi uyg‘onish vaqti mavjud.
• Ish bajarilish tarixi holati (ok, skipped, error).
• Heartbeat o‘tkazib yuborish sabablari (quiet-hours, requests-in-flight, alerts-disabled).

• cron: scheduler disabled; jobs will not run automatically → cron o‘chirilgan.
• cron: timer tick failed → rejalashtiruvchi tik muvaffaqiyatsiz; fayl/log/runtime xatolarini tekshiring.
• heartbeat skipped va reason=quiet-hours → faol soatlar oynasidan tashqarida.
• heartbeat: unknown accountId → heartbeat yetkazib berish manzili uchun yaroqsiz accountId.

• /automation/troubleshooting
• /automation/cron-jobs
• /gateway/heartbeat

​

Ulangan tugun vositasi ishlamaydi

openclaw nodes holati
openclaw nodes describe --node <idOrNameOrIp>
openclaw approvals get --node <idOrNameOrIp>
openclaw logs --follow
openclaw status

• Tugun kutilgan imkoniyatlar bilan onlayn.
• Kamera/mikrofon/joylashuv/ekran uchun OS ruxsatlari berilgan.
• Exec tasdiqlashlari va allowlist holati.

• NODE_BACKGROUND_UNAVAILABLE → tugun ilovasi oldingi rejimda bo‘lishi kerak.
• *_PERMISSION_REQUIRED / LOCATION_PERMISSION_REQUIRED → OS ruxsati yetishmaydi.
• SYSTEM_RUN_DENIED: approval required → exec tasdiqlashi kutilmoqda.
• SYSTEM_RUN_DENIED: allowlist miss → buyruq allowlist tomonidan bloklangan.

• /nodes/troubleshooting
• /nodes/index
• /tools/exec-approvals

​

Brauzer vositasi ishlamaydi

openclaw browser holati
openclaw browser start --browser-profile openclaw
openclaw browser profiles
openclaw logs --follow
openclaw doctor

• Yaroqli brauzer bajariluvchi fayli yo‘li.
• CDP profili yetib borilishi.
• profile="chrome" uchun kengaytma relay yorlig‘i biriktirilgan.

• Failed to start Chrome CDP on port → brauzer jarayoni ishga tushmadi.
• browser.executablePath not found → sozlangan yo‘l yaroqsiz.
• Chrome extension relay is running, but no tab is connected → kengaytma relesi ulangan emas.
• Browser attachOnly is enabled ... not reachable` → faqat ulash (attach-only) profili uchun yetib boriladigan maqsad yo‘q.

• /tools/browser-linux-troubleshooting
• /tools/chrome-extension
• /tools/browser

​

Agar yangilashdan keyin birdan nimadir buzilib qolgan bo‘lsa

​

1. Autentifikatsiya va URLni almashtirish xatti-harakati o‘zgardi

openclaw gateway holati
openclaw config get gateway.mode
openclaw config get gateway.remote.url
openclaw config get gateway.auth.mode

• Agar gateway.mode=remote bo‘lsa, CLI chaqiruvlari masofaviy manzilga yo‘naltirilayotgan bo‘lishi mumkin, lokal xizmatingiz esa sog‘lom bo‘lsa ham.
• Aniq --url bilan qilingan chaqiruvlar saqlangan hisob ma’lumotlariga qaytmaydi.

• gateway connect failed: → noto‘g‘ri URL manzili.
• unauthorized → endpoint yetib boriladi, ammo autentifikatsiya noto‘g‘ri.

​

2. Bind va autentifikatsiya himoya cheklovlari qat’iylashdi

openclaw config get gateway.bind
openclaw config get gateway.auth.token
openclaw gateway status
openclaw logs --follow

• Loopback bo‘lmagan bindlar (lan, tailnet, custom) uchun autentifikatsiya sozlangan bo‘lishi kerak.
• gateway.token kabi eski kalitlar gateway.auth.tokenni almashtirmaydi.

• refusing to bind gateway ... without auth → bind + auth mos kelmasligi.
• RPC probe: failed runtime ishlayotgan paytda → gateway tirik, ammo joriy auth/url bilan kirish imkonsiz.

​

3. Juftlash va qurilma identifikatsiyasi holati o‘zgardi

openclaw devices list
openclaw pairing list <channel>
openclaw logs --follow
openclaw doctor

• Dashboard/nodlar uchun kutilayotgan qurilma tasdiqlashlari.
• Siyosat yoki identifikatsiya o‘zgarishlaridan keyin kutilayotgan DM juftlash tasdiqlashlari.

• device identity required → qurilma autentifikatsiyasi qondirilmagan.
• pairing required → jo‘natuvchi/qurilma tasdiqlanishi kerak.

openclaw gateway install --force
openclaw gateway restart

• /gateway/pairing
• /gateway/authentication
• /gateway/background-process