question: Offline — server unreachable

[chtgogenz-art]

[diegosouzapw]

Thanks for the report. The panel in your screenshot is doing its job — that status means the probe found nothing listening at http://localhost:20128.

What the extension actually checks: it sends HEAD /v1/models to the configured Server URL. Even a 401/403 (key required) counts as online — so this is not an API-key problem. "Offline — server unreachable" only appears on connection refused / timeout: no OmniRoute server is reachable at that address from the machine where VS Code runs.

Quick diagnosis, in order:

1. Is OmniRoute installed and running? In a terminal on the same machine as VS Code:

   curl -I http://localhost:20128/v1/models

   • Any HTTP response (200/401/403) → the server is up; hit Save & Test again.
   • connection refused / timeout → the server isn't running there.
2. Not installed yet? npm install -g omniroute && omniroute (or npx omniroute@latest), then open http://localhost:20128 in a browser to confirm the dashboard loads. The panel's "Install OmniRoute" link covers this too.
3. Running somewhere else? If OmniRoute runs in Docker, WSL, or on another machine, localhost from VS Code's point of view is not that place — put the real address in SERVER URL (e.g. http://<host-ip>:20128). Docker needs the port published (-p 20128:20128).
4. Custom port? If you set the PORT env var, mirror it in the URL.

Could you share: how you run OmniRoute (npm, npx, Docker, from source — or not installed yet), the setup (everything on one machine? WSL? remote?), and what the curl above returns? With that we can pin it down immediately.