2.0 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-10-20 | 2026-10-20 |
|
high |
Restore OpenRouter connectivity
Symptoms
- TLS connection hangs
- Model requests time out
- Other providers still work
Procedure
- Check session activity; ensure previous HTTPS calls completed.
- Review last WARP errors.
- Restart the Hermes process with the GoOp tool.
- Send a small test completion request.
- 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
GoOpbinary;hermeshas 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:
- Confirm OpenRouter is not a standalone provider in the first place —
custom_providersin~/.hermes/config.yamlholds onlylitellm,guacano,Omniroute:20128,command-codeandomni-101. See systems/openrouter.- If the failure is a fallback failure, use runbooks/test-openrouter and check the six entries of the live chain.
- Restart with
systemctl --user restart hermes-gateway.service(not "the GoOp tool").- 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.
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.