Help Centre
› Uptime Kuma
› Uptime Kuma notifications not sending
Monitors detect downtime correctly but alerts never arrive. This guide covers the common causes across email, chat and webhook channels with step-by-step diagnostics.
Diagnosing the problem •
Email notifications not sending •
Slack / Discord / Teams not delivering •
Telegram not responding •
Webhook failing •
Pushover not arriving •
When to contact SmartXHosting •
FAQ
- Test the notification channel — Settings › Notifications › edit the channel › Test. If Test works but monitors don’t trigger, issue is in monitor-channel assignment.
- Check monitor-channel assignment — edit the monitor, scroll to Notifications section, confirm the channel is enabled.
- Check status history — did the monitor actually go down? Sometimes the monitor stayed up.
- Review recent notifications log — Uptime Kuma logs attempts. Settings › Notifications › Logs if enabled.
- Check spam folder — automated alerts often flagged initially. Mark as “not spam” to train filter.
- Gmail App Password expired — regenerate in Google Account › Security › App Passwords.
- SMTP credentials rotated — update in Uptime Kuma Notifications.
- Port blocked — some networks block 587. Try 465 with SSL/TLS.
- SPF/DKIM/DMARC on sender domain — email providers may silently reject unauthenticated messages. Configure DNS records.
- Sending limit reached — Gmail 500/day personal, 2000/day Workspace. Switch to a transactional service (SendGrid, Mailgun) via HTTP Request node for volume.
- Webhook URL revoked — Slack Apps or Discord Integrations page lets you regenerate. Paste new URL.
- Channel deleted — webhook points to deleted channel. Create a new webhook for current channel.
- Rate limiting — Slack Tier 1 methods limit to ~1/sec. Bursts of monitor alerts may be throttled.
- Microsoft Teams Workflows — if webhook stopped working after migration, recreate with Workflows connector (Office 365 connectors deprecated).
- Bot Token wrong — verify via BotFather.
@BotFather › /mybots › select bot › API Token.
- Chat ID wrong — for groups, must be negative. Send a message to the group, then check
https://api.telegram.org/bot<TOKEN>/getUpdates.
- Bot not in group — add the bot to the group first.
- Bot blocked by group admin — check group settings.
- Endpoint URL changed — external service may have rotated the webhook. Update URL.
- Endpoint returns 4xx/5xx — receiving service rejects the payload. Check endpoint logs.
- Custom body syntax error — invalid template causes silent failure. Clear custom body and test.
- Auth header wrong — check Additional Headers JSON is valid.
- User Key / App Token wrong — re-copy from Pushover dashboard.
- App limit reached — Pushover free tier limits to 10,000 notifications/month. Upgrade if you exceed.
- Phone in Do Not Disturb — set Pushover priority to Emergency which overrides.
- Pushover app signed out — re-sign in on the device.
Open a support ticket if:
- Test fails for all channels simultaneously (infrastructure issue)
- SMTP Test works but notifications from monitors don’t fire
- Notifications worked yesterday and stopped without changes
- Uptime Kuma logs show attempts but no delivery
UK support for notification issues
SmartXHosting support can diagnose SMTP, webhook, and chat notification issues from the server side. Open a ticket via the Customer Dashboard.
Open a support ticket
Q: Notification Test works but no real alert.
A: Check monitor-channel assignment. Edit the monitor, scroll to Notifications, enable the channel.
Q: Email notifications working, Slack not.
A: Slack webhook revoked or channel deleted. Regenerate webhook URL in Slack.
Q: Telegram bot not responding.
A: Bot must be added to the group. Check Bot Token and Chat ID. Test with curl first.
Q: All notifications stopped at once.
A: Likely platform issue. Check SmartXHosting status and contact support. Rare but possible.
Q: Too many alerts for one incident.
A: Set Resend Notification lower, or disable it entirely. By default Uptime Kuma sends one alert on transition to down.