BeszelAgentManager v2.8.0 — Release Notes (from v2.7.3)
Highlights
- Hub URL IP Fallback is now reliable: detects hub/proxy outages correctly, switches to fallback, and switches back when the primary recovers — with clear logging.
- New “Extra” tab: tune fallback behavior (check interval, failover threshold, restore threshold) from the GUI.
Hub URL IP Fallback Improvements
-
Failover now reacts to real reachability issues (not only DNS resolution).
-
Added recovery switching: automatically restores to the primary hub once it’s healthy again.
-
Hardened detection to handle edge cases like HTTP 404 responses during proxy failures.
-
Improved logging so it clearly shows:
- when it’s counting failures/successes,
- when it switches to fallback,
- and when it restores to primary.
New “Extra” Tab
- Added a new Extra tab (next to Agent Logging) with fallback controls:
- Check interval (seconds)
- Fail over after (failures)
- Restore after (successes)
- Reset-to-defaults option
- UI & UX Improvements
- Cleaned up the bottom status bar to look less cluttered.
- Made autosave feedback more visible so it’s harder to miss.
- Fixed the “white background blocks” behind status text.
- Stability / Regression Fixes
- Fixed Apply settings regressions introduced during autosave/fallback work.
- Fixed missing handler and helper issues that caused crashes (e.g. hub-status click handler).
- Fixed autosave validation issues (argument mismatch handling for _safe_int).
- Fixed missing imports (apply_service_env_only) causing task failures.
- Re-hardened NSSM “Edit service” to prevent the black console window from reappearing.
Upgrade note: This release contains major improvements to fallback behavior. If you use Hub URL IP Fallback, check the new Extra tab to confirm your desired failover/restore thresholds.