#Silent agent — no replies (dashboard/Telegram) after clean Ubuntu reinstall

1 messages · Page 1 of 1 (latest)

north lark
#

Problem
Fresh Ubuntu install (Lenovo IdeaPad 3-15ADA05, kernel 6.17.0-20-generic, Node 22.22.2). OpenClaw 2026.4.15 installs & onboarding completes, but agent is completely silent. Messages accepted, yet no response appears in dashboard (127.0.0.1:18789) or Telegram (@Lutiekbot).
This exact issue repeats every time after clean reinstalls (npm uninstall -g openclaw + rm -rf ~/.openclaw + reboot + fresh install). Started right after today's Ubuntu reinstall.
Key status --deep summary

Gateway: running, reachable, RPC probe OK, systemd active
Telegram: ON + OK (token valid)
OpenRouter: auth OK, probe succeeds (~18s)
Session: openrouter/auto or /free
Memory: enabled (memory-core) but unavailable

Tried repeatedly

Skipped most onboarding options (skills, plugins, hooks)
openclaw gateway restart, systemctl restart, model pinning (/model openrouter/free etc.)
/new, /reset, new sessions, hard refresh
openclaw logs --follow (no clear errors)
openclaw doctor (archived orphan file)
Multiple full clean uninstall/reinstall cycles

Gateway, auth & channels look healthy — agent never replies.
Reproducibility
100% on this machine post-Ubuntu reinstall. Did not occur on previous setup.
Extra info available

Full logs after test message
openclaw config get
openclaw pairing list telegram
systemctl --user status openclaw-gateway.service

Looks like system-level issue on Ubuntu 6.17 (AppArmor? systemd user session? kernel/loopback? missing libs?) that survives clean reinstalls.
Happy to run any debug commands.

novel egretBOT
tough schoonerBOT
#

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

novel egretBOT
uncut hemlockBOT
#

Let me check the local docs/source for the exact current wording before I suggest anything.

#

Thanks, this is a really solid report.

Because the dashboard and Telegram both accept the message, but no reply ever materializes, I would not chase Telegram, AppArmor, or loopback first. This looks more like one of these:

  1. service config drift, Config (cli) vs Config (service)
  2. agent stuck in bootstrap/session init
  3. model runtime passes probe, but fails on a real agent run

Can you paste this exact batch:

openclaw gateway status --deep
openclaw status --all
openclaw sessions --all-agents --json
openclaw infer model run --model openrouter/auto --prompt "Reply with exactly: smoke-ok" --json
openclaw infer model run --model openrouter/free --prompt "Reply with exactly: smoke-ok" --json
#

Then in another terminal:

openclaw logs --follow

Send one dashboard test message, then paste the log lines from that moment.

What I’m looking for:

  • Config (cli) != Config (service)
    First fix to try:
    openclaw gateway install --force
openclaw gateway restart