Hermes

Hermes Desktop stuck on "Connecting"

Last checked

The error

[backend] Hermes gateway is ready
[fleet-roster] local: Gateway ticket bootstrap failed
[hermes:api GET /api/profiles] Error: Gateway ticket bootstrap failed

desktop.log from the Microsoft Store build of v0.22.1 (issue #138906). A deleted profile instead logs "Profile '<name>' does not exist" (issue #149590).

Desktop is waiting for a gateway that never hands it a usable session. Three causes are on record: the v0.22.1 Microsoft Store build (fixed in v0.22.2), a profile you deleted that Desktop still routes to on Windows, and SSH gateways whose remote side never answers. Update first, then read the last lines of desktop.log to see which one you have.

Why it happens

Desktop shows Connecting while it asks a local or remote gateway for a session. If the gateway is up but refuses or never answers that request, Desktop keeps retrying instead of showing an error screen.

  1. The v0.22.1 Microsoft Store build was made from the wrong commit; the gateway reported ready but every request failed with Gateway ticket bootstrap failed (issue #138906). v0.22.2 is the release v0.22.1 was meant to be.
  2. A deleted profile. On Windows, active-profile.json can still point Desktop at a profile you removed, and hermes gateway ensure fails with Profile '<name>' does not exist on every boot (issue #149590, open on 10 November 2026).
  3. An SSH or remote gateway. Desktop can sit on Connecting and then report Timed out waiting for the remote dashboard to announce it (issue #146389, open).

The fix

  1. 1 Update Hermes. Store installs update through the Microsoft Store; v0.22.2 or later fixes the Store build.
  2. 2 Open desktop.log and read the lines just before the retry loop.
  3. 3 If it names a profile that does not exist, open %APPDATA%\Hermes\active-profile.json, set the profile in defaultRoute back to default, and restart Desktop.
  4. 4 For an SSH gateway, check that Hermes is installed and current on the remote machine and run hermes gateway status there.
hermes gateway status

Still failing?

  • Run hermes gateway status on the same machine to see whether the gateway is running and which profile it serves.
  • If Desktop instead shows Hermes couldn't start, follow that page.

Related errors

Full guideHermes Agent Not Working? 14 Errors and Their Exact Fixes

Hit a different error?

Paste any agent error and get the cause and fix in seconds.

Open the decoder

Frequently asked questions

My gateway says it is ready. Why does Desktop still say Connecting?

Ready means the gateway process is up. Desktop still needs a session ticket from it, and the Store v0.22.1 build and the deleted-profile bug both fail at that step.

Will editing active-profile.json lose anything?

No. It only tells Desktop which profile to open first. Your profiles and chats stay in the Hermes data folder.

Stop firefighting agent errors

Decoding errors one at a time is the manual version of what BetterClaw automates. Run your agents on a no-code AI agent platform with managed models, retries and config validation built in.

Deploy Your Agent — Start FreeBook a Demo

Free plan available · Pro $49/mo · BYOK · 7-day free trial