telegram sendMessage failed: Network request for 'sendMessage' failed!
I've installed Openclaw in a VPS. I installed everything, but I can't interact with the bot using telegram. Responeses are received just to dashboard and not to telegram. Sometimes I get some messages to telegram but not answers
I ran several commands:
root@srv890380:~# openclaw gateway status
OpenClaw 2026.2.14 (c1feda1) — It's not "failing," it's "discovering new ways to configure the same thing wrong."
│
◇
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-02-15.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=loopback (127.0.0.1), port=18789 (service args)
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: stopped (state inactive, sub dead, last exit 0, reason 1)
RPC probe: failed
RPC target: ws://127.0.0.1:18789
gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: cli --url
Config: /root/.openclaw/openclaw.json
Service is loaded but not running (likely exited immediately).
File logs: /tmp/openclaw/openclaw-2026-02-15.log
Logs: journalctl --user -u openclaw-gateway.service -n 200 --no-pager
I ran several commands:
root@srv890380:~# openclaw gateway status
OpenClaw 2026.2.14 (c1feda1) — It's not "failing," it's "discovering new ways to configure the same thing wrong."│
◇
Service: systemd (enabled)
File logs: /tmp/openclaw/openclaw-2026-02-15.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=loopback (127.0.0.1), port=18789 (service args)
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: stopped (state inactive, sub dead, last exit 0, reason 1)
RPC probe: failed
RPC target: ws://127.0.0.1:18789
gateway closed (1006 abnormal closure (no close frame)): no close reason
Gateway target: ws://127.0.0.1:18789
Source: cli --url
Config: /root/.openclaw/openclaw.json
Service is loaded but not running (likely exited immediately).
File logs: /tmp/openclaw/openclaw-2026-02-15.log
Logs: journalctl --user -u openclaw-gateway.service -n 200 --no-pager
The AI that actually does things. Emails, calendar, home automation - all from your favorite chat app. New shell, ready to help. The lobster way.
134,827Members
Resources
Similar Threads
Was this page helpful?
