Files
agent-estate-wiki/runbooks/restore-openrouter.md
T
Hermes 341dda95dd stocktake 2026-11-11: 36 stale pages re-verified (0 stale); fallback chain rewritten 4/6 slots; CT333 'clawtest' naming claim corrected; nous 404 credits signature replaces refresh-token 401; estate shrank (VM 310 + CT601 gone)
- freshness: 36 stale / 93 fresh / 3 no-date -> 0 stale / 129 fresh / 3 no-date of 132 (same-day report regenerated after the corrections, per pattern 13)
- skills: 299 skills / 67 categories (count unchanged; generator arithmetic re-verified by hand against the live tree: 300 SKILL.md files - 1 nested duplicate = 299)
- runbooks/test-openrouter: live fallback chain rewritten (primary back to smart-route/custom:omni-101; mimo-v2.5, stepfun, qwen3.5/ollama-cloud out; guacano + kilo-reflection-beam-free in); ollama.com dropped from the URL test list; guacano/litellm noted as internal + key-gated
- comparisons/hermes-vs-nanobot: the 2026-10-20 'CT333 is zeroclaw in Proxmox naming' claim was itself wrong - pct list and hostname both return clawtest
- incidents/2026-10-22-nous: refresh-token failure gone from logs; new signature 404 insufficient_credits_for_paid_model from auxiliary.pulse_memory (ninth slot, back on nous, paid model) - open item revised
- incidents/2026-08-29-gmail: email crons now ok but root cause unfixed 74 days (himalaya message read still in fetch_newsletters.py; goimapnotify back up PID 441; monitor still paused)
- 30 further pages re-verified live and de-flagged with dated probe notes (ct207 ingress, CT205 guanaco v0.8.15, CT270 nextcloud 33.0.2.2, headless stack, hermes-ui both hosts, systemd units + cgroup limits, terminal/tool_search/mnemosyne/custom_providers config blocks, ops profile still deleted, hosts/pve guest lists)
- log.md addendum + index.md date bump; no page deleted, no secrets written
2026-11-11 03:52:48 +08:00

2.3 KiB

title, type, status, created, updated, verified_on, tags, sources, confidence
title type status created updated verified_on tags sources confidence
Restore OpenRouter connectivity runbook active 2026-07-22 2026-11-11 2026-11-11
runbook
openrouter
recovery
high

Restore OpenRouter connectivity

Symptoms

  • TLS connection hangs
  • Model requests time out
  • Other providers still work

Procedure

  1. Check session activity; ensure previous HTTPS calls completed.
  2. Review last WARP errors.
  3. Restart the Hermes process with the GoOp tool.
  4. Send a small test completion request.
  5. Confirm tool calling works.

⚠ This runbook is out of step with the current install (flagged 2026-10-20). Steps 2 and 3 reference WARP and a "GoOp tool" — neither exists on this box. There is no WARP client configured and no GoOp binary; hermes has no such subcommand. The steps are carried over from a different install and were not executed during the 2026-10-20 review.

The procedure that actually applies here:

  1. Confirm OpenRouter is not a standalone provider in the first place — custom_providers in ~/.hermes/config.yaml holds only litellm, guacano, Omniroute:20128, command-code and omni-101. See systems/openrouter.
  2. If the failure is a fallback failure, use runbooks/test-openrouter and check the six entries of the live chain.
  3. Restart with systemctl --user restart hermes-gateway.service (not "the GoOp tool").
  4. Send a small test completion and confirm tool calling works.

Last successfully used: 2026-06-22 — which predates every configuration referenced on this page. Treat the page as unverified until someone runs it end to end. The "out of step" flag re-confirmed 2026-11-11. There is still no GoOp binary (which GoOp and /usr/local/bin/GoOp, /opt/GoOp all absent), no GoOp subcommand in hermes --help, and no WARP process (pgrep -af warp empty) and no WARP client configured. The substitute procedure recorded on 2026-10-20 is therefore still the correct one.

Verification

A test prompt returns successfully through OpenRouter.

Escalation

If the failure persists, check DNS, certificate expiry and provider status.

Last successfully used

2026-06-22 — 120 days ago. This is the single oldest verification date still in the wiki alongside the original 2026-07-22 page set.