From a6af16062707d1534e2123a63fdfa5932da12f10 Mon Sep 17 00:00:00 2001 From: William Mantly Date: Tue, 28 Jul 2026 17:57:28 -0400 Subject: [PATCH] Release 1.8.2: audit records carry the real upstream-connect error as failDetail (#21) --- CHANGELOG.md | 5 +++++ nodejs/package.json | 2 +- 2 files changed, 6 insertions(+), 1 deletion(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index 0e14469..08ecbb8 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -4,6 +4,11 @@ All notable changes to this project are documented here. Format loosely follows [Keep a Changelog](https://keepachangelog.com/en/1.1.0/); versions correspond to git tags (`vX.Y.Z`) and `nodejs/package.json`'s `version`. +## [1.8.2] - 2026-07-28 + +### Fixed +- **Audit records for a failed upstream connection only ever said `upstream-unreachable`** — `resolveAndConnect` discarded the real error from `connectUpstream` (ECONNREFUSED, ETIMEDOUT, an ssh2 auth-failure message, etc.) and replaced it with that one generic string, so there was no way to tell a network-layer failure from an auth failure from the audit log alone. This is what blocked root-causing the "Could not reach 192.168.1.206" (emby host) report — the real error is now captured and surfaced as a new `failDetail` field on the audit record, shown as a tooltip on the fail badge in the admin audit table. + ## [1.8.1] - 2026-07-28 ### Fixed diff --git a/nodejs/package.json b/nodejs/package.json index bc9b5ff..74ff8c3 100644 --- a/nodejs/package.json +++ b/nodejs/package.json @@ -1,6 +1,6 @@ { "name": "t42-jump-host", - "version": "1.8.1", + "version": "1.8.2", "description": "SSH jump host for the theta42 stack — LDAP-authenticated, directory-driven host bridging with audit and metrics", "author": [ {