Icon of Uptime Kuma app on Umbrel App Store

Uptime Kuma

Self-hosted uptime monitoring tool

Louis Lam

Open App Store on your umbrelOS device to install this app
Screenshot 1 of Uptime Kuma app on Umbrel App Store
Screenshot 2 of Uptime Kuma app on Umbrel App Store
Screenshot 3 of Uptime Kuma app on Umbrel App Store
About this app

Uptime Kuma is a self-hosted monitoring tool like Uptime Robot.

Features:

  • Monitoring uptime for HTTP(s) / TCP / HTTP(s) Keyword / Ping / DNS Record / Push / Steam Game Server.
  • Fancy, Reactive, Fast UI/UX.
  • Notifications via Telegram, Discord, Gotify, Slack, Pushover, Email (SMTP), and 70+ notification services.
  • 20 second intervals.
  • Multi Languages
  • Simple Status Page
  • Ping Chart
  • Certificate Info
What's new
Version 2.0.2last week

⚠️ This is a major version update with some breaking changes. Make sure to have a backup of your data. After the update, a migration will run. This process may take a few minutes, depending on how many monitors you have.

Key highlights in this release:

  • Added new notification providers: Nextcloud Talk, Brevo, and Evolution API
  • Improved login with autofocus on 2FA
  • Added Slovak language to the dropdown menu
  • Various UI improvements and bug fixes

Security updates:

  • Fixed a Local File Inclusion vulnerability in the Real-Browser monitor feature
  • Addressed a Server-side Template Injection issue in Notification Templates

Full release notes can be found at https://github.com/louislam/uptime-kuma/releases

Version 1.23.1610 months ago

🚨 This release includes important security fixes for a Local File Inclusion vulnerability in the Real-Browser monitor feature.

Full release notes can be found at https://github.com/louislam/uptime-kuma/releases

Version 1.23.15last year

This release includes a couple bugfixes.

Full release notes can be found at https://github.com/louislam/uptime-kuma/releases

Version 1.23.13-pushlast year

This release brings Push monitor functionality to Uptime Kuma on umbrelOS. Push monitors allow you to ping your Uptime Kuma instance from external services/servers to act as a check-in.

Full release notes for Uptime Kuma versions can be found at https://github.com/louislam/uptime-kuma/releases

Version 1.23.13last year

This release updates Uptime Kuma from version 1.23.12 to 1.23.13 and includes the following bug fixes:

  • Fixed language setting issues: Localisation-matching algorithm missing some edgecase
  • Fixed TLS issues: Getting TLS certificate through proxy & prometheus update

Full release notes can be found at https://github.com/louislam/uptime-kuma/releases

Version 1.23.12last year

This release updates Uptime Kuma from version 1.23.7 to 1.23.12 and includes various improvements, security fixes, and bug fixes.

Full release notes can be found at https://github.com/louislam/uptime-kuma/releases

Version 1.23.7last year

⚠️ Due to a security fix in this update, all login sessions will be logged out after updating to this version. If you are using some unofficial/3rd party tools, you may need to re-generate an auth token.

This release updates Uptime Kuma from version 1.23.3 to 1.23.7.

💇‍♀️ Improvements:

  • Show the original timeout message again and +10 seconds for abort signal
  • Improved error message on abort signal timeout (Thanks @chakflying)

🐛 Bug Fixes:

  • Fixed a memory leak issue. Close the client postgresql connection after rejection. (Thanks @mvaled)
  • Reverted "Restart running monitors if no heartbeat", which causes some issues from 1.23.4 to 1.23.6.

⬆️ Security Fixes

  • An XSS issue in the "Google Analytics ID" text field (Reported by @gtg2619) (Read more: GHSA-v4v2-8h88-65qj)
  • Rewrite Tailscale ping using spawnSync (Reported by @vaadata-pascala) (Read more: GHSA-v4v2-8h88-65qj)
  • getGameList, testChrome are no longer accessible without login

Full changelog for versions 1.23.3 to 1.23.7 can be found here: https://github.com/louislam/uptime-kuma/releases

Version 1.23.3last year

Updates Uptime Kuma from version 1.23.0 to 1.23.3

Warning: Due to the security fix, all login sessions will be logged out, after updated to this version. Important: If you are using some unofficial/3rd party tools, it could be a breaking change. You may need to re-generate an auth token. 🐛 Bug Fixes:

  • Fixed an issue that notification is not working if the config is too long
  • Enable status page certificate expiry badge for all HTTP(s) monitors
  • Fixed kafka producer bugs
  • Fixed an issue that x-forwarded-host is not being used correctly
  • Fixed a race condition issue that some data is not being saved in the status page editor if you clicked it too fast

⬆️ Security Fixes

  • Fixed persistent session tokens issue. There was no way to revoke session tokens even if you changed the password. Now you can revoke them by changing your password if you think they may be leaked (Read more: GHSA-g9v2-wqcj-j99g). Full changelog for versions 1.21.2 to 1.23.0 can be found here: https://github.com/louislam/uptime-kuma/releases
Version 1.23.02 years ago

Updates Uptime Kuma from version 1.21.2 to 1.23.0. 🐻 It should be the last minor version of Uptime Kuma v1. I will focus on the development of v2. Stay tuned! Update: The last minor version (1.23.x) means that there won't be any new features introduced in v1. However, bug fixes will still be provided. You can expect to see 1.23.1, 1.23.2 and so on.

🆕 New Features:

  • Added an improved comprehensive monitor list filtering
  • Added an ability to bulk select, pause & resume
  • Added an ability to show certificate expiry on status pages
  • Added Tailscale ping monitor
  • Added badges for status page status

💇‍♀️ Improvements to Maintenance:

  • Dropdown menu is no longer blocked by the save button bar
  • Added an ability to configure a custom PushDeer server URL
  • Added an ability to set TLS certs (Put ca.pem, key.pen and cert.pem in the data/docker-tls/your_hostname/)
  • Strip trailing slashes to avoid 404 from Home Assistant's API endpoint

🐛 Bug Fixes:

  • Fixed Redis authentication reattempt issue
  • Fixed notification toggle missing when import from backup
  • Fixed the issue that IPv6 addresses could not be displayed in the log
  • Avoid new timezones or non-existing timezones crash Uptime Kuma
  • Fixed SMTP notification "Ignore TLS Error" option

⬆️ Security Fixes

  • Hardening: Avoid exposing the Uptime Kuma version to the public

Full changelog for versions 1.21.2 to 1.23.0 can be found here: https://github.com/louislam/uptime-kuma/releases

Version 1.21.22 years ago

Updates Uptime Kuma from version 1.19.6 to 1.21.2.

🆕 New Features:

  • Now you can schedule maintenance with a cron expression + duration

💇‍♀️ Improvements to Maintenance:

  • The core of maintenance feature is completely rewritten and is changed to cron based, the performance is much better
  • Effective Date Range is no longer required, it is now optional
  • Ability to set a timezone per maintenance
  • Ability to follow the timezone with DST

🐛 Bug Fixes:

  • #3003 Maintenance is completely bugged in 1.21.1 and 1.21.0
  • #2988 Fix Ignore TLS/SSL Error is not working when using a proxy (Thanks @chakflying)

⚠️ IMPORTANT - After upgrading, you should review the following maintenance items:

  • All old maintenance schedules will be set to UTC individually, if you need other timezones, please change it individually.
  • Since previous versions' maintenance is always respected to UTC, which means the maintenance time could be shifted due to DST in your country.
  • Breaking change: Due to the limitation of cron, the options Last 2nd day of month, Last 3rd day of month and Last 4th day of month in the strategy Day of Month is no longer available. (Last day of month is still available)

Full changelog for versions 1.19.6 to 1.21.2 can be found here: https://github.com/louislam/uptime-kuma/releases

Version 1.19.62 years ago

From 1.18.5 to 1.19.6:

  • Fix Ping monitor is not working on Windows
  • Fix Security patch from upstream dependencies (knex.js)
  • Add Splunk Notification Provider (Thanks @Joseph-Irving)
  • Fix Maintenance count is incorrect
  • Fix Ping monitor issues after 1.9.4
  • Fix Postgres monitor do not handle some error cases correctly

⚠️ Attention

  • Server side timezone is configurable now, you should check whether it is correct in the Settings.
  • As current DNS cache mechanism is not working properly in some IPv6 networks, DNS cache is now turned off by default. Turn this back on manually in Settings page if you need this. Full changelog can be found here: https://github.com/louislam/uptime-kuma/releases
Version 1.18.52 years ago

From 1.18 to 1.18.5:

  • Add free.fr SMS notification (Thanks @CL0Pinette)
  • Add GoAlert Notification (Thanks @mhkarimi1383)
  • Add SMSManager Notification (Thanks @jakubenglicky)
  • Add ServerChan Notification (Thanks @mjysci)
  • Add new notification: Line Notify (Thanks @0x01code)
  • Add new notification: Home Assistant notification (Thanks @rmtsrc)
  • Add label to status badge (Thanks @woooferz)

Full changelog can be found here: https://github.com/louislam/uptime-kuma/releases

Version 1.17.13 years ago
  • Add settings for notification of certificate expiry (Thanks @chakflying)
  • Cache DNS records on HTTP(s) monitor (Thanks @gregdev)
  • Add new monitor type: MS SQL Server (Thanks @christopherpickering)
  • Add new notification: ntfy (Thanks @philippdormann)
  • Add NTML Auth Option for HTTP(s) (Thanks @christopherpickering)
  • Pre-render some html for status page such as title and meta tag
  • Optimize page load time by Gzip or Brotli
  • [HTTP Keyword] Show some pure text body (first 50-char) in notification when keyword not found
  • Handle page not found (Thanks @domingospanta)
  • Reduce monitoring log - Smaller log size and disk usage
  • Fix upside down mode issue for push monitors (Thanks @kaysond)
  • Fix default notifications are not enabled
  • Fix Lunasea do not send general message
  • Fix cloudflared cannot be stopped in No Auth mode
Version 1.16.13 years ago
Information