VIGILWEB · PUSH SETUP
Vigilweb Push Notification Setup
Vigilweb can send optional alerts to a push or chat provider you control. No Vigilweb push backend or second app is required. These instructions require Vigilweb 0.4.1 or later.
In the app, open Alert settings → Push notifications, choose one provider, enter its details, enable push, save, and send a test push.
Before you start
- Install the provider's app on the phone that should receive alerts and allow its notifications.
- HTTPS is required for every provider. Plain HTTP endpoints are rejected.
- Credentials are encrypted on the device with Android Keystore.
- Only one push provider is active at a time. Saving changes cancels queued push alerts from the previous configuration.
- Automatic alerts require the monitoring phone to be powered, online and running. A test push can run while monitoring is stopped.
Pushover
Pushover is a personal push app with a one-time purchase per platform. Vigilweb includes a built-in Pushover application token, so users normally enter only their User Key. Recommended: use your own Pushover application token and User Key to avoid the shared Vigilweb monthly message quota.
- Install Pushover from Google Play or the App Store and sign in or create an account.
- Get your User Key from pushover.net or the Pushover app settings. It is private; do not share it.
- Optional but recommended: sign in at pushover.net/apps, create your own application token, and copy the API/Application Token. Keep it private.
- In Vigilweb, select Pushover, enter your User Key, optionally switch on your own application token and enter it, enable push, save, and send a test push.
Limits: Pushover currently allows up to about 10,000 messages per month per application on the free API tier. The built-in Vigilweb token is shared among Vigilweb users. A user-owned application token avoids the shared quota. The Pushover client app purchase and terms are your responsibility.
Troubleshooting: HTTP 400/401/403 usually means a wrong User Key, a wrong or revoked application token, or a token from another Pushover account. If no notification appears, check the Pushover app's device list and its Android/iOS notification settings.
ntfy
ntfy is a free and open-source push service. Use the public ntfy.sh server or a self-hosted server with HTTPS.
- Install the ntfy app on the receiving phone, or open your self-hosted ntfy web UI.
- Choose a server URL: https://ntfy.sh, or your self-hosted HTTPS URL.
- Choose a long random topic and subscribe to it in the ntfy app. Anyone who knows a public ntfy.sh topic can subscribe, so treat the topic as a secret.
- If the topic is protected, create an access token in ntfy and enter it in Vigilweb.
- In Vigilweb, select ntfy, enter the server URL and topic, enter the access token if required, enable push, save, and send a test push.
Limits: ntfy.sh rate limits, message size limits, caching and retention apply. Self-hosted server availability, TLS and security are your responsibility.
Troubleshooting: HTTP 401/403 means the topic or access token is not authorized. HTTP 404 usually means the server URL or topic path is wrong. Check the ntfy app subscription and its Android/iOS notification settings.
Slack
Slack alerts post to a channel through an incoming webhook. You need permission to install an app in the workspace.
- Sign in to Slack in a browser and open api.slack.com/apps, then choose Create New App → From scratch.
- Name the app, choose the workspace and create it. Open Incoming Webhooks and activate them.
- Choose Add New Webhook to Workspace, select the channel that should receive alerts, and allow access.
- Copy the webhook URL shown for that channel. It starts with https://hooks.slack.com/services/ and is a secret.
- In Vigilweb, select Slack, paste the webhook URL, enable push, save, and send a test push.
Each webhook posts to one channel. Create another webhook if you need another channel. Workspace admins may need to approve installation, and Slack rate limits and policies apply.
Troubleshooting: HTTP 404 or 410 means the webhook was deleted or the channel was archived; recreate it. HTTP 403 means the app was removed or posting is blocked. Check the Slack app's notification settings if your phone does not notify you.
Discord
Discord alerts post to a channel through a channel webhook.
- Open Discord on desktop or the web and go to the server and channel that should receive alerts.
- Open the channel settings → Integrations → Webhooks and choose New Webhook.
- Give it a name, confirm the channel, and copy the Webhook URL. It starts with https://discord.com/api/webhooks/ and is a secret.
- In Vigilweb, select Discord, paste the webhook URL, enable push, save, and send a test push.
You need permission to manage webhooks in that channel. Each webhook posts to one channel. Discord may rate-limit busy webhooks; Vigilweb retries using the provider's delay.
Troubleshooting: HTTP 401/403/404 means the webhook was deleted or disabled, or channel permissions changed. HTTP 429 is rate limiting. Check the Discord app's notification settings and the channel's notification preferences.
Telegram
Telegram alerts are sent by a bot that you create. You need a bot token and a chat ID.
- Install Telegram on the receiving phone and sign in.
- Open a chat with @BotFather and send /newbot. Choose a display name and a username ending in bot, then copy the bot token. It is a secret.
- Start a chat with your bot and press Start, or add the bot to a group with permission to post.
- Get the chat ID: use @userinfobot for a personal chat, or send a message to your bot and open
https://api.telegram.org/bot<YOUR_BOT_TOKEN>/getUpdatesand find chat.id. For a group, use the negative chat ID from getUpdates or @userinfobot. For a public channel, use @channelname if the bot is an administrator allowed to post. - In Vigilweb, select Telegram, enter the bot token and chat ID, enable push, save, and send a test push.
Clear the browser history after using getUpdates because the token appears in the URL. Group privacy mode may prevent the bot from reading messages; sending requires the bot to be in the chat with permission to post. Telegram rate limits apply.
Troubleshooting: HTTP 400/401/403 means an invalid token, the bot was blocked, or the bot lacks access to the chat. Check the Telegram app's notification settings and the chat's mute state.
Generic webhook
Use this for a self-hosted push gateway, home automation, or an unsupported service. The endpoint must accept an HTTPS POST with Content-Type application/json.
POST <your-url>
Content-Type: application/json
Authorization: Bearer <optional-token>
{
"app": "Vigilweb",
"schema": 1,
"event": "down",
"title": "Example is down",
"message": "Vigilweb: Example is down. HTTP 503. ...",
"timestamp": 1762870800000
}The event is down, up, certificate or test. The monitored URL and query string are not included. If a bearer token is configured, it is sent as an Authorization header. Any 2xx response is accepted; 408, 429 and 5xx are retried; other 4xx responses are permanent; redirects are not followed.
Common troubleshooting
- Delivery history shows the provider's HTTP status and a safe error; it does not confirm that the phone displayed the notification.
- The provider app's own Android/iOS notification settings control whether its notifications are visible. Check those first.
- If a test fails, verify the provider account, channel/topic/chat permissions, and the credentials saved in Vigilweb.
- Never paste webhook URLs, ntfy topics or access tokens, bot tokens, Pushover User Keys or application tokens into support messages.
- Automatic alerts require the monitoring phone to be powered, online and running. A test push does not require monitoring to be running.
Policies
Privacy Policy · Terms & Conditions
Vigilweb is available on Google Play.
For questions, contact support@piemobileapps.com.