Unraid

Repeat alerts until acknowledged

Plugin 2026.10.08 and later can repeat an alert until someone takes notice. It is off by default. Set Repeat alerts until acknowledged to Enabled and every notification that arrives as an Unraid alert comes back every Repeat every seconds (300 by default, 30 to 3600) until you tap Acknowledge on one of your devices, or until Stop repeating after runs out (3600 by default, 60 to 10800). Warnings and info notices never repeat. The test notification is sent as an alert, so it is an easy way to try it.

• When a later notification for the same event is not an alert, such as Unraid's notice that a disk returned to normal, the plugin stops that event's repeats before sending it, so the remaining repeats do not cover the good news. The repeats of other events carry on.
• Notifications sent without an event name (Unraid's notify without -e) are grouped by their subject instead, so each subject counts as one event (2026.10.08a and later).
• Turning the setting off does not stop repeats that are already running. Those stop when someone acknowledges them or when they expire.
• Each repeating alert is tagged unraid-<server name>, lowercased with dashes. The CLI can stop all of them at once, as long as it uses the same API key as the plugin.
• An account can have at most 25 repeating alerts at once. When it is full, or PushWard refuses the acknowledge for another reason, the plugin sends the alert once as an ordinary notification rather than lose it.

pushward receipt cancel --tag unraid-tower

How the button, the repeats and their limits work is covered on the acknowledged alerts page.

End-to-end encryption

With a key set, plugin 2026.10.08 and later encrypt the title, subtitle, body and link of every notification on the Unraid server itself before it is sent. PushWard stores and forwards an envelope it cannot open, and your devices decrypt it with the same key.

1. In the PushWard app (1.17.0 or later), open Settings > End-to-End Encryption, create a key and copy it.
2. Paste it into End-to-end encryption key and click Apply. The status cards show its Key ID, which should match the one in the app.

The page never shows the stored key: leaving the field empty keeps it, pasting another one replaces it, and Remove key turns encryption off. An hlk_ API key pasted there is refused.

• PushWard can still read the level, the server name, the timestamp and the importance, the name of the Live Activity a notification links to (such as tower-array), and the repeat tags when repeating is on, which carry the server name. The event name is not sent readable. Repeats of one event still replace each other's banner because they share an identifier made from it, and from 2026.10.08a that identifier is derived from your encryption key, so it cannot be turned back into the event name.
• A link is encrypted only as a full http:// or https:// address. A link that is a web UI path gets the server's web UI address in front of it (the Unraid web UI URL setting, or the address Unraid detects), and is left out when that is unknown.
• The encrypted text has to fit in about 2.2 KB, so a long message is shortened, the body first.
• Live Activities (parity, mover, backups, UPS) and widgets are not encrypted, so the jobs they track are visible to PushWard either way.
• If the key is not valid, or PHP on the Unraid server has no AES-256-GCM, notifications still go out but without their details ("Unraid alert on Tower"). The system log says why, and the encryption card on the Settings tab turns red.
• An API key that belongs to an organization cannot send encrypted notifications. From 2026.10.08a the plugin then sends the alert without its text, as it does for a key that is not valid.

The key is saved with the rest of the settings on the flash drive. What exactly is covered, and what a device without the key shows, is on the end-to-end encryption page.