Push Notifications
Get alerts on your phone or desktop as native notifications. Tindra talks to the browsers' own push services (Web Push), so there's no relay, no app store, and no third-party account. Push needs Tindra 1.6.0 or later.
Turn push on for a device
Push is set up per device, by each person, for themselves.
- Open Tindra on the device, in the browser or as an installed app.
- Go to Settings > Profile > Notifications.
- Switch on Push notifications on this device and allow notifications when the browser asks.
- Click Send test next to the device. A "Tindra test notification" should show up within seconds.
The device list shows every device you turned push on for, when it was added, when it last got a notification, and how many deliveries failed. The current one is marked This device. Use Remove for devices you no longer use. Each person can have up to 20.
iPhone and iPad
Safari on iOS and iPadOS only offers push to web apps on the Home Screen. Tap Share, then Add to Home Screen, and open Tindra from the new icon. Then turn push on as above. This needs iOS or iPadOS 16.4 or later.
When the switch is greyed out
The profile section tells you why:
| Message | Fix |
|---|---|
| Push notifications need Tindra to be served over HTTPS. | Browsers only offer push on https:// or localhost. See Self-hosting. |
| On iPhone and iPad, add Tindra to your Home Screen first | See iPhone and iPad. |
| Notifications are blocked for this site. | You denied the permission prompt earlier. Allow notifications for this site in the browser settings, then try again. |
| This browser does not support push notifications. | Use a current Chrome, Edge, Firefox, or Safari. |
| Push notifications are not available on this server. | Ask whoever runs your instance. |
Send alerts to push
Create or edit a rule in Alerts and pick Push notification as the action. Then choose who gets it under Notify. You start out as the only pick. Everything else about the rule works like any other alert rule.
Each person gets the alert on every device where they turned push on. Tapping the notification opens the matching issue, monitor, or logs view.
A few things to know:
- Every alert is its own notification. A newer one never replaces an older one.
- Offline devices catch up. Push services hold an alert for up to 24 hours.
- Nobody with a device means a failed firing. If none of the people on the rule have turned push on, the firing shows as failed with
no recipient has a device registered for push notifications. Check the rule's delivery history. - Retries skip devices that already got it. If some devices miss an alert because of an outage or a timeout, the retry goes to those devices only, so nobody gets it twice.
- An enabled push rule needs at least one person. If everyone on a rule is deleted, it shows Nobody. Pick someone before you turn it on again.
When devices get removed
Tindra drops a device on its own when:
- the push service says it's gone (HTTP 404 or 410), for example after you uninstall the app or clear site data, or
- five deliveries in a row failed because of the device, spread over at least 72 hours.
Test notifications never count as failures. Neither do failures while the push service also fails for everyone else, so a broken setup on your instance doesn't wipe your devices.
Your account and your devices
- Changing your password removes your other devices. The one you changed it on keeps push.
- A password reset removes all of your devices.
- Logging out removes the device you log out on.
- Deleting a user removes their devices and takes them off every push rule.
API tokens and the MCP server can't see who a rule notifies, and MCP can't create push rules. Create those in the web UI.
Install Tindra as an app
Install Tindra and it opens in its own window with the Tindra icon. Nothing is cached offline, so the app always shows live data and needs a connection.
| Where | How |
|---|---|
| Chrome or Edge on desktop | Click the install icon in the address bar, or find Install in the browser menu. |
| Safari on macOS | File > Add to Dock |
| Chrome on Android | Menu, then Add to Home screen or Install app |
| Safari on iPhone and iPad | Share, then Add to Home Screen |
On phones, the issue list has a Select toggle in its header. Turn it on and taps on rows select issues instead of opening them. A bar along the bottom offers Resolve, Ignore, and a menu with Unignore and Merge. Touch tablets always show the checkboxes.
Self-hosting
On managed instances push works out of the box. Self-hosted, check three things.
HTTPS. Serve Tindra over https:// and set PUBLIC_URL to match. See Reverse proxy.
Outbound access. Tindra has to reach the push services over HTTPS. If your firewall limits outbound traffic, allow these:
fcm.googleapis.comandroid.googleapis.com*.push.services.mozilla.com*.push.apple.com*.notify.windows.com
Devices can only register on these push services. Tindra never follows redirects from them. For a browser that uses its own push service, add its hosts with PUSH_EXTRA_HOSTS. Push delivery blocks private addresses like webhooks do, so a push service on your own network also needs WEBHOOK_ALLOW_PRIVATE_IPS=true.
The VAPID key. Tindra generates its push key on first start and stores it in the database, so your database backup carries it. If the key changes, every device has to turn push on again. Restore the database together with the rest of the instance and nothing changes.
| Variable | Default | Description |
|---|---|---|
VAPID_PRIVATE_KEY |
Generated | Pins your own key instead: a base64url P-256 private key, as printed by npx web-push generate-vapid-keys. Changing it invalidates every registered device. |
VAPID_SUBJECT |
From PUBLIC_URL |
The contact push services can reach you at. Defaults to your PUBLIC_URL when it's https. If you set it, it must be a mailto: address or an https: URL, or Tindra won't start. Unset with a non-HTTPS PUBLIC_URL, Tindra logs a warning at startup, because Safari then rejects every notification. |
PUSH_EXTRA_HOSTS |
Empty | Extra push service hosts, comma separated. Host names only, no scheme or port. *.example.com matches subdomains. |
See Configuration for the rest of the server settings.