--- title: Restore OpenRouter connectivity type: runbook status: active created: 2026-07-22 updated: 2026-10-20 verified_on: 2026-10-20 tags: [runbook, openrouter, recovery] sources: [] confidence: 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. ## 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.