Skip to content

Hermes Console Setup v1.5.2

Latest

Choose a tag to compare

@xP3ta xP3ta released this 11 Sep 04:25
· 8 commits to main since this release

Installer for connecting a self-hosted Hermes Agent to Hermes Console. Validated on Windows, Unix and macOS.

Install

Windows -- PowerShell 5.1+ as Administrator:

irm https://raw.githubusercontent.com/xP3ta/hermes-setup/main/hermes-mobile-setup.ps1 | iex

Linux / macOS / Termux:

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

Replace main with setup-v1.5.2 for a frozen, hash-verifiable revision.

What changed

Windows: pairing could be silently broken by a dismissed firewall prompt.

Windows creates inbound block rules for an executable when the "allow this app
on private/public networks?"
dialog is dismissed. Block rules win over allow rules,
so the services kept listening, setup reported every check as passed, and no other
device on the network could reach the phone-facing ports -- an install that looked
perfect and could never pair.

Setup now:

  • creates the firewall permissions (port rules and per-application rules) before
    any service starts listening, because the prompt appears at that exact moment;
  • removes the enabled inbound block rules that cover the managed executables (only
    those, and only the programs it manages), since an allow rule cannot outrank them.

If your previous install was in that state, running this revision repairs it: the
block rules are cleared and the application rules are added without touching the
verified port rule.

Everything from v1.5.1 and v1.5.0 is included: branded banner and progress bar on
Windows and Unix, the pairing result (ASCII QR, link and image path) in the console,
service port overrides, the progress-driven Dashboard readiness wait, phone-facing
address candidates and -Uninstall / -Uninstall -Purge.

Validated on

  • Windows 10/11 and Windows Server: full install, rerun, rollback, custom ports and uninstall; reviewer suite 319 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: the source is the truth, which is what makes the installed bytes verifiable by hash.