github marcpope/borgbackupserver v2.53.1

4 hours ago

Two bug fixes.

#264 — Agent update failure email spam

When an update_agent job failed mid-upgrade (network blip mid-download, read timeout, etc.), the scheduler's auto-update step re-queued the same job every minute. Each retry hit the same failure and emailed admins directly via Mailer::notifyFailure(), so admins got one email per agent per minute, indefinitely, until the network issue resolved.

The skip-if-pending check only looked at queued/sent/running jobs, not failed ones. Added a 24-hour backoff: if any update_agent for this agent has failed within the last 24 hours, skip the auto-queue. Once the cooldown expires we try once more — if it fails again, one fresh email, then another 24 hours of silence. Caps the spam at one email per agent per day.

The deeper consistency fix (routing the failure email through NotificationService so it picks up the dedup/escalation we built for backup_failed, and shows in the notification bell) is deliberately left for a future release — the backoff solves the actual problem reported here without touching a working code path.

#261 — Custom brand logos look wrong

Custom logos uploaded via Settings → Branding inherited CSS that was hand-tuned for the default Borg mascot — absolute-positioned "peek over the topbar" geometry for the navbar logo, edge-to-edge no-padding framing plus a heavy drop-shadow for the login art. Looked off for any logo that wasn't the specific bundled mascot.

Custom uploads now get their own classes:

  • Topbar: constrained max-height/max-width with object-fit: contain and small padding, no absolute positioning. Logo sits inside the navbar instead of bleeding past it.
  • Login art: 24 px of padding, and the drop-shadow filter is removed (it looked wrong on logos that already had their own shadow or a white background).

The default Borg art and mascot are unaffected — they still get the original treatment.

Notes

  • Agent and server versions remain synchronized at 2.53.1.
  • Docker image rebuilds automatically via GitHub Actions.
  • No migrations; in-place server update is sufficient.

Don't miss a new borgbackupserver release

NewReleases is sending notifications on new releases.