Skip to content

Hermes Console Setup v1.4.0

Choose a tag to compare

@xP3ta xP3ta released this 11 Sep 01:57
· 18 commits to main since this release

One-command installer that connects a self-hosted Hermes Agent to Hermes Console. This is the revision validated on Windows, Unix and macOS.

Install

Windows -- PowerShell 5.1+ as Administrator:

irm https://raw.githubusercontent.com/xP3ta/hermes-setup/setup-v1.4.0/hermes-mobile-setup.ps1 -OutFile "$env:TEMP\hermes-setup.ps1"
& "$env:TEMP\hermes-setup.ps1"

Linux / macOS / Termux:

curl -fsSL https://raw.githubusercontent.com/xP3ta/hermes-setup/setup-v1.4.0/hermes-mobile-setup.sh | sh

What changed

Windows and Unix

  • Service ports can be moved with HERMES_GATEWAY_PORT, HERMES_DASHBOARD_PORT and HERMES_BRIDGE_PORT. Defaults are unchanged (8642 / 9119 / 9131). An invalid, out-of-range or duplicated value stops the run before anything is modified, so a port owned by another process no longer forces you to kill it.
  • Dashboard readiness now extends while the Dashboard is really building (its task still running, or its log still growing), up to 30 minutes, with an explicit trail in the log. It fails bounded when nothing progresses, so a real failure cannot hide behind a long wait.
  • Pairing probes up to three candidate addresses and adopts the one that actually answers, re-verifying the firewall rule when the address kind changes. A machine with a VPN, Hyper-V/WSL adapters or a second NIC no longer fails with an address the phone cannot reach.

Windows

  • -Uninstall and -Uninstall -Purge: removes only what the installer created (its own Scheduled Tasks, its own firewall rules and the pairing artifacts) and is idempotent. -Purge also removes the Hermes home, and refuses a path that is not a recognisable Console home.
  • Every bounded failure now points at -Diagnose, which writes a redacted report — no tokens, API keys or pairing credentials.

macOS

  • Fixed: the installer did not parse under the system /bin/sh (bash 3.2).
  • Fixed: the service runners could not find Node/npm, because launchd does not inherit the session PATH, so the Dashboard never started and the install failed.
  • Linux-only contract checks are now skipped with a reason on other platforms instead of being reported as failures.

Mobile Bridge -- unchanged in this release: 1.18.1. Its download is verified against a closed manifest (size, SHA-256 and source version) before anything runs.

Validated on

  • Windows 10/11 and Windows Server: full install, rerun, rollback, custom ports and uninstall; reviewer suite 275 checks, zero skips, under Windows PowerShell 5.1 and PowerShell 7.
  • Debian with systemd: full install, idempotent rerun, authenticated probes; contract suite 36 checks.
  • macOS (Apple Silicon): BSD /bin/sh syntax, a real launchctl service lifecycle, and a full isolated install whose three services answer authenticated probes while a protected route rejects an anonymous request.

Not validated natively: Intel macOS, Linux ARM64/Termux, Windows ARM64, and a public HTTPS deployment behind a reverse-proxy certificate.

Notes

  • Setup is plain, auditable source -- read it before running.
  • No telemetry and no hosted relay.
  • No installer binaries are attached to this release: the tag is the source of truth, which is what makes the installed bytes verifiable by hash.