A Proxmox backup can fail at 2 AM while everything else keeps running normally.

Your VMs are still up. The host looks healthy. Nothing forces you to open the backup logs.

Then a few days later you discover that the backup you assumed was running every night hasn’t been working.

For backups, I don’t want another monitoring dashboard.

I want this:

❌ PBS backup FAILED
node pve1 · 02:14

One message when the backup breaks.

How Proxmox Backup Notifications Work

Proxmox VE and Proxmox Backup Server include a notification system that can route events to different notification targets.

The exact targets and fields depend on the installed release. Start with the current Proxmox notification system documentation rather than copying a webhook body from an older release.

Depending on your setup, those targets can include email, Gotify, and webhooks.

Webhook notifications are particularly useful because they let Proxmox send an HTTP request to another service when an event occurs.

A webhook can include notification data such as:

title
message
severity
timestamp
fields

Matchers can then control which notifications reach a target.

That means you don’t necessarily have to forward every informational event. You can route the events you actually care about — such as errors from backup jobs.

The Problem With Proxmox Backup Alerts

There are already plenty of ways to monitor a homelab.

You can run Prometheus and Grafana. You can use Netdata, Gotify, email alerts, or build a much larger monitoring stack.

Those tools make sense when you want to monitor the whole environment.

But backup failures are a much narrower problem.

I don’t need another page showing CPU usage, memory utilization, disk graphs, load averages, or 30 days of metrics.

I need to know whether the backup worked.

If it failed, tell me.

Telegram Notifications for Failed Proxmox Backups

Proxmox webhook notifications make a simple flow possible:

Proxmox / PBS
      ↓
backup failure
      ↓
webhook
      ↓
Telegram alert

The result could be as simple as:

❌ PBS backup FAILED
node pve1 · 02:14

There is another important detail here: the receiver should ideally live outside the Proxmox host it is monitoring.

If your alerting service dies together with your homelab, it can’t tell you that something went wrong.

A tiny external receiver avoids that problem.

Backup Alert Validation Test (Closed)

In September 2026, I tested exactly that idea for RunAHomeLab.

Not a monitoring platform. Not another dashboard.

Just:

Proxmox backup failed → one Telegram message.

Before adding accounts, billing, history, or integrations, I built a small test to see whether Proxmox users wanted it.

How the Telegram Validation Test Worked

The closed test did not connect to a Proxmox server.

It sent an example of what a failed backup notification would look like:

✅ Test alert delivered

This is what you'd get when a Proxmox/PBS backup fails:

❌ PBS backup FAILED
node pve1 · 02:14

Participants could indicate whether they would connect an alert service to their Proxmox or PBS server. The test stored a random session token and event timestamps for up to 30 days. It used a Telegram chat ID in memory to deliver the example but did not store that ID in its application database. It did not accept Proxmox payloads.

The validation test is closed. It no longer accepts Telegram test requests; the source code remains public.

What I’d Build If People Actually Want It

The first real version would stay deliberately small:

  • a personal webhook URL
  • failed Proxmox/PBS backup alerts
  • Telegram delivery
  • basic node/job information
  • no agent running in your homelab
  • no monitoring dashboard

Proxmox would send the backup notification to the external receiver, and the receiver would forward the useful part to your Telegram chat.

That’s it.

What About a Backup That Never Runs?

There is a second failure mode that’s arguably even more dangerous.

An explicit backup failure can produce an error notification.

But what if the expected backup doesn’t happen at all?

For example, if something prevents the scheduled job from running, there may be no failed backup event to forward.

An external receiver could eventually solve this too by tracking the last successful backup.

Instead of waiting for an error, it could notice:

⚠️ No successful backup received
node pve1 · 26 hours

That would catch a different class of backup problems.

That was not part of the validation test.

The validation test was intended to answer the simpler question:

Do enough Proxmox users want one-message backup alerts in the first place?

Validation Status

The validation test ended on September 28, 2026. No production alert service was launched. For an active setup, use the Proxmox notification targets and matchers described earlier in this guide.