A fancy self-hosted monitoring tool

Louis Lam

Last update: Jan 3, 2023

Overview

Uptime Kuma

It is a self-hosted monitoring tool like "Uptime Robot".

Features

Monitoring uptime for HTTP(s) / TCP / Ping.
Fancy, Reactive, Fast UI/UX.
Notifications via Webhook, Telegram, Discord, Gotify, Slack, Pushover, Email (SMTP) and more by Apprise.
20 seconds interval.

How to Use

Docker

# Create a volume
docker volume create uptime-kuma

# Start the container
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1

Browse to http://localhost:3001 after started.

Change Port and Volume

docker run -d --restart=always -p <YOUR_PORT>:3001 -v <YOUR_DIR OR VOLUME>:/app/data --name uptime-kuma louislam/uptime-kuma:1

Without Docker

Required Tools: Node.js >= 14, git and pm2.

git clone https://github.com/louislam/uptime-kuma.git
cd uptime-kuma
npm run setup

# Option 1. Try it
npm run start-server

# (Recommended) 
# Option 2. Run in background using PM2
# Install PM2 if you don't have: npm install pm2 -g
pm2 start npm --name uptime-kuma -- run start-server

# Listen to different port or hostname
pm2 start npm --name uptime-kuma -- run start-server -- --port=80 --hostname=0.0.0.0

Browse to http://localhost:3001 after started.

(Optional) One more step for Reverse Proxy

This is optional for someone who want to do reverse proxy.

Unlikely other web apps, Uptime Kuma is based on WebSocket. You need two more headers "Upgrade" and "Connection" in order to reverse proxy WebSocket.

Please read wiki for more info: https://github.com/louislam/uptime-kuma/wiki/Reverse-Proxy

One-click Deploy

How to Update

Docker

Re-pull the latest docker image and create another container with the same volume.

For someone who used my "How-to-use" commands to install Uptime Kuma, you can update by this:

docker pull uptime-kuma:1
docker stop uptime-kuma
docker rm uptime-kuma
docker run -d --restart=always -p 3001:3001 -v uptime-kuma:/app/data --name uptime-kuma louislam/uptime-kuma:1

PS: For every new release, it takes some time to build the docker image, please be patient if it is not available yet.

Without Docker

git fetch --all
git checkout 1.0.10 --force
npm install
npm run build
pm2 restart uptime-kuma

What's Next?

I will mark requests/issues to the next milestone. https://github.com/louislam/uptime-kuma/milestones

More Screenshots

Settings Page:

Telegram Notification Sample:

Motivation

I was looking for a self-hosted monitoring tool like "Uptime Robot", but it is hard to find a suitable one. One of the close one is statping. Unfortunately, it is not stable and unmaintained.
Want to build a fancy UI.
Learn Vue 3 and vite.js.
Show the power of Bootstrap 5.
Try to use WebSocket with SPA instead of REST API.
Deploy my first Docker image to Docker Hub.

If you love this project, please consider giving me a ⭐ .

Contribute

If you want to report a bug or request a new feature. Free feel to open a new issue.

If you want to modify Uptime Kuma, this guideline maybe useful for you: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md

English proofreading is needed too, because my grammar is not that great sadly. Feel free to correct my grammar in this Readme, source code or wiki.

Comments

A complete maintenance planning system
Description

This pull request includes the addition of maintenance planning functionality.

Affected monitors are not tested during maintenance, but status "3" (MAINTENANCE) is returned. No notifications are also sent during maintenance. Notifications will only be sent if the monitor status after maintenance is "DOWN" (MAINTENANCE -> DOWN).

Due to the addition of this function, the UI has also been changed (adding buttons, texts, ...).

This pull request also requires the addition of some new translations.

Related issue: #191

Type of change

Please delete any options that are not relevant.

User interface (UI)

New feature (non-breaking change which adds functionality)

Breaking change (fix or feature that would cause existing functionality to not work as expected) - shouldn't

Checklist

[x] My code follows the style guidelines of this project

[x] I ran ESLint and other linters for modified files

[x] I have performed a self-review of my own code and tested it

[x] I have commented my code, particularly in hard-to-understand areas

[x] My changes generate no new warnings

[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)
opened by karelkryda 45
Avoid CPU Usage Spikes by improving the healthcheck script
⚠️ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡️ Security Policy

[X] I agree to have read this project Security Policy

Description

There are very high CPU usage spikes every 3-5 minutes. Does this align with any database cleanup tasks that run and how do I disable or lengthen the time between those operations?

👟 Reproduction steps

I have a mixture of TCP pings and HTTP pings. Nothing out of the ordinary. I also have a Prometheus query that runs every 1 minute to get the statistics from UptimeKuma

👀 Expected behavior

I would expect maybe a few spikes every hour or so or no spikes at all (after all its just pinging a web page)

😓 Actual Behavior

I am getting spiky CPU usage every 3 minutes that is maxing out 1 core.

🐻 Uptime-Kuma Version

1.18.5 but this has progressed across multiple versions

💻 Operating System and Arch

Raspberry Pi, arm

🌐 Browser

NA

🐋 Docker Version

Docker 20.10.13

🟩 NodeJS Version

NA

📝 Relevant log output

No response
feature-request
opened by bwees 42

Reverse proxy broken (`ERR_TOO_MANY_REDIRECTS 308` on Chrome)

Is it a duplicate question? Don't think so.

Describe the bug With the latest louislam/uptime-kuma:1.7.3-alpine docker container, reverse proxy can no longer be used and the following error appears with both caddy and https-portal.

By reverting to louislam/uptime-kuma:1.6.0-alpine resolves this issue:

To Reproduce Steps to reproduce the behavior:

Run the following docker-compose.yaml file:

version: '3.3'

services:
  https-portal:
    image: steveltn/https-portal:1
    ports:
      - '80:80'
      - '443:443'
    links:
      - uptime-kuma
    restart: always
    environment:
      DOMAINS: 'example.com -> http://uptime-kuma:3001'
      STAGE: 'production' # Don't use production until staging works
      # FORCE_RENEW: 'true'
      WEBSOCKET: 'true'
    volumes:
      - https-portal-data:/var/lib/https-portal

  uptime-kuma:
    image: louislam/uptime-kuma:1.7.3-alpine
    volumes:
      - ./uptime-kuma:/app/data
    ports:
      - 3001:3001

volumes:
  https-portal-data:

Info Uptime Kuma Version: 1.7.3 Using Docker?: Yes Docker Version: 20.10.8 OS: Centos 8 Browser: chrome, safari

help Unknown

opened by vwxyzjn 42

Push-based monitoring

Is it a duplicate question? Not that I'm aware (after searching "push", "push-based", and "healthchecks).

Is your feature request related to a problem? Please describe. Nope

Describe the solution you'd like A push-based system where computers (potentially behind NATs) can ping uptime-kuma to indicate that it's up. This allows for arbitrary checks (can run any command and report its status). One project that implements this is healthchecks.io. It would be awesome if we can have integration with Healthchecks.io.

Describe alternatives you've considered healthchecks.io. Though there's no readily available dashboard implementations that show historical uptime.

Additional context N/A
feature-request

opened by ben-z 40
[Request] Allow public access to dashboard

First of all, this project looks awesome, with statping being unmaintained this is an amazing replacement!

I would like to request the addition of some sort of public dashboard like other services have (statping, etc). I use these apps to monitor the status of a few services I run and I would like for my users to be able to check the service's status (like I currently do with tinystatus, but also like statping)

Thank you.
feature-request

opened by zmiguel 39
Synchronize push monitor heartbeats to api calls (fixes #1422)
Description

Fixes #1422.

The goal is to avoid the race condition caused by creating heartbeats and checking them in two different, asynchronous functions, which is exacerbated by the possible drift of heartbeat checking due to setTimeout behavior.

The basic idea is that before we do a setTimeout(beat), we check when the last heartbeat arrived, and adjust the timeout such that the next check happens 1 heartbeat interval after the last heartbeat. This prevents the heartbeat check from drifting relative to the api call (which usually happens on a fixed interval like a cron job).

A 1s buffer time is added to that timeout to ensure that the heartbeat check happens after the api call is expected. This helps avoid the race condition that occurs when the heartbeat check and api call happen simultaneously (which they will tend to do). The buffer time may need to be increased, but the tradeoff is a delay in when the DOWN notification is sent in the event of a missed heartbeat.

It may be desirable to make the buffer time user-controlled.

Right now, retries aren't explicitly addressed. I would propose that in the case of missed heartbeats, the monitor reverts to checking exactly every heartbeat interval (i.e. ignoring the time of the last heartbeat).

This seemed to me to be the best way to address the issue without making huge architectural changes (i.e. make the heartbeat checking happen in the router function).

Please let me know if this all looks ok and I can finish it up, and finish testing, linting/formatting, etc.

Type of change

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] My code follows the style guidelines of this project

[x] I ran ESLint and other linters for modified files

[x] I have performed a self-review of my own code and tested it

[x] I have commented my code, particularly in hard-to-understand areas

[x] My changes generate no new warnings

[x] My code needed automated testing. I have added them (this is optional task)
opened by kaysond 38
Feature/monitor checks
This PR adds more options for checking the response of http requests.

You can perform these checks:

This changes the structure of the http requests a bit. It combines the http and http keyword into one option.

For the http option you can then define certain checks:

The PR also automatically converts existing checks so that the 'accepted_statuscodes' and 'keyword' are converted to a monitor_check row:

accepted_statuscodes => {monitor_id: 1, type: 'HTTP_STATUS_CODE_SHOULD_EQUAL', value: '["200-299"]'}

keyword => {monitor_id: 1, type: 'RESPONSE_SHOULD_CONTAIN_TEXT', value: 'my keyword'}

This conversion also happens for imports from a json backup.
opened by bertyhell 36
Unable to log into uptime-kuma. Get strange error.

I am running the container in docker on an unraid server. It has been running for 6 days and is still monitoring hosts and sending alerts however I am unable to log in to the web portal. The logs give this error over and over:

(node:18) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag --unhandled-rejections=strict (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 592)
High help

opened by jim361tx 31
Simple Domains Like Google.com are Getting `getaddrinfo EAI_AGAIN` Errors
Describe the bug I have about 10 domains I am watching, 7 of my own domains and 3 common domains, I recently installed piHole and I noticed 3 of my domains, 2 common and 1 of mine, started failing all the time. I looked into it and seems as these all are getting getaddrinfo EAI_AGAIN errors. I would understand if it was only my own domains but the common ones like Google and Reddit are weird. I looked at the logs within Portainer and I am not seeing any errors being thrown only Heartbeat <number>. The two common domains that are failing are www.google.com and www.reddit.com. If I click on the links within Uptime-Kuma I successfully get to the sites.

Expected behavior Better Logging?

Desktop (please complete the following information):

Uptime Kuma Version: 1.0.6

Using Docker?: Yes

OS: Ubuntu 20.04 LTS

Browser: Firefox/Chrome

Additional context Uptime-Kuma is in same Docker-Compose as piHole and have house router running through piHole now.
bug question
opened by tucker19 28
Added MQTT Monitor type
Description

Added MQTT monitor type for monitoring mqtt message and alert if a message is different from preset success message.

Type of change

Please delete options that are not relevant.

New feature (non-breaking change which adds functionality)

Checklist

[x] My code follows the style guidelines of this project

[x] I ran ESLint and other linters for modified files

[x] I have performed a self-review of my own code and test it

[x] I have commented my code, particularly in hard-to-understand areas

[x] My changes generate no new warnings

[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)
opened by tarun7singh 27
Feature monitor the resource over proxy
Description

Added new proxy feature based on http and https proxy agents. Proxy feature works like notifications, there is many proxy could be related one proxy entry.

Supported features

Proxies can activate and disable in bulk

Proxies auto enabled by default for new monitors

Proxies could be applied in bulk to current monitors

Both authenticated and anonymous proxies supported

Export and import support for proxies

HTTP, HTTPS, SOCKS, SOCKS v5 SOCKS v4 protocols are supported

Reviews are welcome 🤩

Fixes #470

Type of change

User Interface

New feature (non-breaking change which adds functionality)

Checklist

[x] My code follows the style guidelines of this project

[x] I ran ESLint and other linters for modified files

[x] I have performed a self-review of my own code and test it

[x] I have commented my code, particularly in hard-to-understand areas

[x] My changes generate no new warnings

Screenshots
opened by ugurerkan 23
HTTP(s) Does not contains or GraphQL Monitors
⚠️ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

Like HTTP(s) - Keyword I need a keyword not in the response.

More context, with graphQL you always get an status code 200, if ok and also if ko. But if ko you will get an json block errors

If I invert the monitor to check if no errors block it's good while endpoint accessible, but if endpoint does not reply it's not detected as a down monitor and always prompt service up.

✔️ Solution

I need a monitor which is UP if keyword not found AND if status code is as I wanted.

❓ Alternatives

more complex but an alternatives is provide an graphql monitor with:

check status code 200

check if errors is in response

header input block

graphql query input block

graphql variables input block

another alternative is to add an check box to avoid keyword in the response in the HTTP(s) keyword monitor, or more powerfull an regexp check in response and it's the user's responsability to setup positive or negative check?

📝 Additional Context

I think the first solution is easy to implement cause it's a duplicate of HTTP(s) - Keyword monitor with a very little change.
feature-request
opened by OlivierMary 0
Custom HTTP methods
⚠️ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷️ Feature Request Type

Other

🔖 Feature description

I'm looking to use a custom HTTP method in a HTTP check. Currently it seems there is a hardcoded list of supported methods, it would be great if we can define a custom HTTP method, so we can monitor non conventional HTTP applications (for example Microsoft remote desktop gateway).

✔️ Solution

Add a field in the dropdown menu that allows a custom value.

❓ Alternatives

No response

📝 Additional Context

No response
feature-request
opened by AvrumFeldman 0
Website assets (CSS/JS/IMG) monitoring
⚠️ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷️ Feature Request Type

New Monitor

🔖 Feature description

Monitor that check all assets (CSS/JS/IMG) on specified page.

Fails if any of assets is unreachable (HTTP 404?).

✔️ Solution

Monitor parse html of specified page fetching URLs to all assets (css/js/img). Then making simple http requests to all gathered URLs.

❓ Alternatives

No response

📝 Additional Context

Sometimes checking only webpage isn't enough, and some websites have auto-generated filenames for assets, so declaring these statically isn't a solution.

Surprisingly, I didn't found that feature in any monitoring system like Uptime Kuma
feature-request
opened by radeksh 1
Force Ping/Check
⚠️ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature, Other

🔖 Feature description

An extra button on the end of "Pause, Edit, Delete" forces a ping of service without needing to wait for "auto check" or to pause and unpause the service.

✔️ Solution

Add a button to the end of the button group that says "Force Check" or something similar, that forces a ping to the service.

❓ Alternatives

Continue pausing and unpausing the service to force a ping.

📝 Additional Context

Something like this maybe?
feature-request
opened by Taylor-Hinote 0
Allow the status page clickable URL to differ from the monitoring URL
⚠️ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷️ Feature Request Type

UI Feature

🔖 Feature description

I can't find any similar requests, but please close if they exist. In the comments of #1885 it is proposed with similar reasoning, but only after the issue has been closed

Can the links shown on the status page (when you enable them next to a service) be different to the links used for a http check?

I am using uptime-kuma to report on the status of my fediverse pages, and so I use https://site.tld/nodeinfo/2.1.json to check the instance is actually working, instead of pinging the base site, but this is not the link I want to allow people to click on the status page because the UI is shown at https://site.tld but the nodeinfo path is for a json file.

I would like to be able to set the link when people click the service on the status page to https://site.tld/ or even https://site2.tld/, while still checking https://site.tld/nodeinfo/2.1.json in the back end.

This could also extend to allowing a URL to be configured for when you are using IP , port or DNS monitors for example, where they otherwise have no option.

✔️ Solution

Allow the links on the status page for http to differ from the monitoring url, either by configuring it in the status page, or the dashboard, perhaps a "Monitoring URL" and a "Display URL", or the status page settings can allow you to change the clickable URL.

❓ Alternatives

I don't think there's an alternative for this.

📝 Additional Context

No response
feature-request
opened by chizutan5 0
Feature: Multiple Users
⚠️⚠️⚠️ Since we do not accept all types of pull requests and do not want to waste your time. Please be sure that you have read pull request rules: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md#can-i-create-a-pull-request-for-uptime-kuma

Tick the checkbox if you understand [x]:

[x] I have read and understand the pull request rules.

Description

This feature, would add the ability to have the main user, (admin user) to add other users, and the main user has the ability to give these users permissions, so they can only view the monitors, status pages etc. Or they can have management permissions, such as add, remove, edit

Fixes #128

Type of change

Please delete any options that are not relevant.

New feature (non-breaking change which adds functionality)

This change requires a documentation update (it could, but it really depends, will leave this here though)

( Just up for discussion and the okay from the project owner (@louislam) before I make any code, as the PR Rules go so none of these apply atm

Checklist

[ ] My code follows the style guidelines of this project

[ ] I ran ESLint and other linters for modified files

[ ] I have performed a self-review of my own code and tested it

[ ] I have commented my code, particularly in hard-to-understand areas (including JSDoc for methods)

[ ] My changes generate no new warnings

[ ] My code needed automated testing. I have added them (this is optional task)

Screenshots (if any)

Please do not use any external image service. Instead, just paste in or drag and drop the image here, and it will be uploaded automatically.
opened by ItIzJR 18

Releases(1.19.2)

1.19.2(Dec 26, 2022)
Fix the UI broken after removed a monitor

Source code(tar.gz)
Source code(zip)
dist.tar.gz(4.33 MB)
1.19.1(Dec 26, 2022)
Fix HTTP Monitor issues occurred in 1.19.0

Fix Docker monitor cannot send notifications (Known platform: Discord) (@zImPatrick)

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @augustin64
Source code(tar.gz)
Source code(zip)
dist.tar.gz(4.33 MB)
1.19.0(Dec 23, 2022)
Merry Xmas! 🐻🎄

🎇 Updates & Fixes

Maintenance Feature (#1213) (Thanks @karelkryda)

Temporary disable notifications during a time window

Show a maintenance message on status pages

Add gRPC monitor (Thanks @minhhoangvn)

Add MySQL monitor (Thanks @Computroniks)

Add socks5h support (Thanks @jbrunner)

Add SMSEagle Notification (Thanks @m-kiszka)

[Ntfy] Add ability to add icon (Thanks @cmeis)

Add configurable server timezone

Log time is now using the server timezone instead of UTC time

Add additional headers option for webhook notifications (Thanks @janhartje)

Fixed entry route not redirecting correctly (Thanks @UltraWelfare)

Add support for custom radius ports (Thanks @Computroniks)

Enable/Disable DNS cache in Settings

Update SQLite to 3.39.4

Fix 'undefined' in link preview generation (Thanks @Dafnik)

Fix sometimes monitor reports unexpected error: "maxContentLength size of -1 exceeded"

Add new language German (Switzerland) (Thanks @saw303)

Improve Docker healthcheck script

Cache uptime values

Fix Invalid Date issues on some Linux environments such as Arch-based Linux or Gentoo Linux

⚠️ Attention

Since 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.

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @MagicFun1241 @cyril59310 @MrEddX @falentio @Saibamen @b-reich @5idereal @Ealrang @cyril59310 @Justman10000 @rbunpat @Johno95CZ
Source code(tar.gz)
Source code(zip)
dist.tar.gz(4.32 MB)
1.19.0-beta.2(Dec 14, 2022)
Maintenance Feature (#1213) (Thanks @karelkryda)

Temporary disable notifications during a time window

Show a maintenance message on status pages

Add gRPC monitor (Thanks @minhhoangvn)

Add MySQL monitor (Thanks @Computroniks)

Add socks5h support (Thanks @jbrunner)

Add SMSEagle Notification (Thanks @m-kiszka)

[Ntfy] Add ability to add icon (Thanks @cmeis)

Add configurable server timezone

Log time is now using the server timezone instead of UTC time

Add additional headers option for webhook notifications (Thanks @janhartje)

Fixed entry route not redirecting correctly (Thanks @UltraWelfare)

Add support for custom radius ports (Thanks @Computroniks)

Enable/Disable DNS cache in Settings

Update SQLite to 3.39.4

Fix 'undefined' in link preview generation (Thanks @Dafnik)

Fix sometimes monitor reports unexpected error: "maxContentLength size of -1 exceeded"

Add new language German (Switzerland) (Thanks @saw303)

Improve Docker healthcheck script

Cache uptime values

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @MagicFun1241 @cyril59310 @MrEddX @falentio @Saibamen @b-reich @5idereal @Ealrang @cyril59310 @Justman10000
Source code(tar.gz)
Source code(zip)
dist.tar.gz(4.33 MB)
1.19.0-beta.1(Dec 5, 2022)
Maintenance (Will add more details later) (#1213) (Thanks @karelkryda)

Add gRPC monitor (Thanks @minhhoangvn)

Add MySQL monitor (Thanks @Computroniks)

Add socks5h support (Thanks @jbrunner)

Add SMSEagle Notification (Thanks @m-kiszka)

[Ntfy] Add ability to add icon (Thanks @cmeis)

Add configurable server timezone

Log time is now using the server timezone instead of UTC time

Add additional headers option for webhook notifications (Thanks @janhartje)

Fixed entry route not redirecting correctly (Thanks @UltraWelfare)

Add support for custom radius ports (Thanks @Computroniks)

Update SQLite to 3.39.4

Fix 'undefined' in link preview generation (Thanks @Dafnik)

Fix sometimes monitor reports unexpected error: "maxContentLength size of -1 exceeded"

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @MagicFun1241 @cyril59310 @MrEddX @falentio @Saibamen @b-reich @5idereal @Ealrang
Source code(tar.gz)
Source code(zip)
dist.tar.gz(4.25 MB)
1.19.0-beta.0(Oct 15, 2022)
Maintenance (Will add more details later) (#1213) (Thanks @karelkryda)

Add configurable server timezone

Log time is now using local timezone instead of UTC time

Fixed entry route not redirecting correctly (Thanks @UltraWelfare)

Add support for custom radius ports (Thanks @Computroniks)

Update SQLite to 3.39.4

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @MagicFun1241
Source code(tar.gz)
Source code(zip)
dist.tar.gz(4.18 MB)
1.18.5(Oct 10, 2022)
Fix misused of jesec in 1.18.4 (Which causes some status page features are broken such as custom css)

Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.90 MB)
1.18.4(Oct 9, 2022)
Fix ntfy issue in 1.18.1 again, username is no longer required

Add Greek Language (Thanks @VasilisThePikachu)

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @wellart @Computroniks @AnnAngela @falentio
Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.89 MB)
1.18.3(Oct 6, 2022)
Add free.fr SMS notification (Thanks @CL0Pinette)

Fix ntfy issue in 1.18.1 (If you are using ntfy, you should update the instance to 1.18.3)

Fix issue when multiple IPs in X-Forwarded-For (Thanks @benscobie)

Hide console window when using ping monitor type on Windows (Thanks @Sympatron)

Other changes

Add a Europe demo server (Thanks @mhkarimi1383)

Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.89 MB)
1.18.2(Oct 4, 2022)
Fix Docker container monitor issue in 1.18.1

Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.79 MB)
1.18.1(Oct 3, 2022)
Add GoAlert Notification (Thanks @mhkarimi1383)

Add SMSManager Notification (Thanks @jakubenglicky)

Add ServerChan Notification (Thanks @mjysci)

Add Squadcast Notification (Thanks @phindmarsh)

Fix Bark (Thanks @zuosc @SuperManito)

Fix Octopush and improve error handling (Thanks @Computroniks)

Add authentication support for ntfy (Thanks @rolfbachmann)

Improve support for password managers (Thanks @ThomasChr)

Add Cypress for e2e testing (Thanks @tamasmagyar)

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @sovushik @ivanbratovic @cyril59310 @mtelgkamp @critical @kdevkr @d3vyce @cunkz @burakurer @rezzorix @Buchtic @Faris0520 @MrEddX @AnTheMaker @SametKUM @Computroniks @5idereal
Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.79 MB)
1.18.0(Sep 5, 2022)
Add new monitor type: Docker container (Thanks @c0derMo)

Add new monitor type: PostgreSQL server (Thanks @christopherpickering)

Add new monitor type: Radius (Thanks @knopwob)

Add ability to resend notification if down X times consequently (Thanks @OidaTiftla)

[Status Page] Ability to set clickable link for https/http monitors (Thanks @Computroniks)

Trust Proxy and read X-Forwarded headers (Thanks @harryzcy, @theS1LV3R, @mhajder)

Add Basque language (Thanks @utolosa002)

Add new notification: AlertNow (Thanks @daeho-ro)

Add new notification: Line Notify (Thanks @0x01code)

Add new notification: Home Assistant notification (Thanks @rmtsrc)

Add new language: Português (Portugal) (pt-PT) (Thanks @mariogarridopt)

Re-introduce DNS caching for http/https monitor (Using cacheable-lookup which is more popular)

Hide mobile footer when not logged in (Thanks @treboryx)

Decrease SQLite query timeout from default to 5 seconds (Thanks @jbenguira)

Add more settings for Bark Notification (Thanks @SuperManito)

Update Apprise from 0.9.9 to 1.0.0 (Release Notes)

Add label to status badge (Thanks @woooferz)

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @MarcHagen @gBasil @thehijacker @jjasghar @Jontes-Tech @Computroniks @5idereal @Deni7 @pemassi @ankhgerel @MrEddX @dtorner @AnnAngela @MrEddX @kiznick @filipporomani @Buchtic @Max-le
Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.76 MB)
1.18.0-beta.0(Aug 13, 2022)
Add new monitor type: Docker container (Thanks @c0derMo)

Add new monitor type: PostgreSQL server (Thanks @christopherpickering)

Add new monitor type: Radius (Thanks @knopwob)

Add ability to resend notification if down X times consequently (Thanks @OidaTiftla)

[Status Page] Ability to set clickable link for https/http monitors (Thanks @Computroniks)

Trust Proxy and read X-Forwarded headers (Thanks @harryzcy, @theS1LV3R, @mhajder)

Add Basque language (Thanks @utolosa002)

Add new notification: AlertNow (Thanks @daeho-ro)

Add new notification: Line Notify (Thanks @0x01code)

Add new notification: Home Assistant notification (Thanks @rmtsrc)

Add new language: Português (Portugal) (pt-PT) (Thanks @mariogarridopt)

Re-introduce DNS caching for http/https monitor (Using cacheable-lookup which is more popular)

Hide mobile footer when not logged in (Thanks @treboryx)

Decrease SQLite query timeout from default to 5 seconds (Thanks @jbenguira)

Add more settings for Bark Notification (Thanks @SuperManito)

Update Apprise from 0.9.9 to 1.0.0 (Release Notes)

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @MarcHagen @gBasil @thehijacker @jjasghar @Jontes-Tech @Computroniks @5idereal @Deni7 @pemassi @ankhgerel @MrEddX @dtorner
Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.73 MB)
1.17.1(Jun 23, 2022)
Fix: Revert Caching DNS records on HTTP(s) monitor #1821

Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.60 MB)
1.17.0(Jun 22, 2022)
⚠️ Unstable, please update to 1.17.1

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

How to update? Please read this: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

Bug report: https://github.com/louislam/uptime-kuma/issues

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @AnnAngela @tamasmagyar @MrEddX @Computroniks @MarcHagen @Saibamen
Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.60 MB)
1.17.0-beta.1(Jun 16, 2022)
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

How to update? Please read this: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

Bug report: https://github.com/louislam/uptime-kuma/issues

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @AnnAngela @tamasmagyar @MrEddX @Computroniks
Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.59 MB)
1.17.0-beta.0(Jun 14, 2022)
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 (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 - Less log size and disk usage

How to update? Please read this: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

Bug report: https://github.com/louislam/uptime-kuma/issues

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @AnnAngela @tamasmagyar @MrEddX
Source code(tar.gz)
Source code(zip)
dist.tar.gz(3.60 MB)
1.16.1(May 29, 2022)
Fix tags that do not show on status pages

Synchronize push monitor heartbeat, fix race condition (Thanks @kaysond)

How to update? Please read this: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

Bug report: https://github.com/louislam/uptime-kuma/issues

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! (Let me know if I forget to add your name if your pull request have been merged in this version) @dhfhfk @furkanipek
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.22 MB)
1.16.0(May 26, 2022)
Add badges API (Wiki will be added later, please read #1119) (Thanks @jensneuber)

Add optional title for Apprise (Fix apprise integration for Zulip Streams) (Thanks @c-w)

Add a new notification: PagerDuty (Thanks @MarcHagen)

Add a new language: ไทย (Thanks @kiznick)

Allow to specify Resolver Port for DNS Monitor (Thanks @Computroniks)

Fix incorrect uptime calculation for push monitors (Thanks @karelkryda)

Fix chart error on switch back to recent (Thanks @chakflying)

Fix aliyun-sms "SignatureDoesNotMatch" Error (Thanks @GOGOsu)

Add service address for more types to Discord notifications (Thanks @jordanbertasso)

How to update? Please read this: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

Bug report: https://github.com/louislam/uptime-kuma/issues

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! @Saibamen @MrEddX @AnnAngela @burakurer
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.19 MB)
1.16.0-beta.0(May 16, 2022)
Add badges API (Wiki will be added later, please read #1119) (Thanks @jensneuber)

Add optional title for Apprise (Fix apprise integration for Zulip Streams) (Thanks @c-w)

Improve Status & HeartBeatBar Styling & Animation (Thanks @raphaelbernhart)

Fixed incorrect uptime calculation for push monitors (Thanks @karelkryda)

Fix chart error on switch back to recent (Thanks @chakflying)

Fix aliyun-sms "SignatureDoesNotMatch" Error (Thanks @GOGOsu)

Add hostname to Discord notifications (Thanks @jordanbertasso)

How to update? Please read this: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

Bug report: https://github.com/louislam/uptime-kuma/issues

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! @Saibamen @MrEddX @AnnAngela
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.17 MB)
1.15.1(Apr 29, 2022)
Fix settings cannot be saved in "No Auth" mode #1577

Add the ability to specify status in the push URL (e.g. /api/push/<TOKEN>?status=down&msg=OMG) (Thanks @trogper)

[Docker] Update Apprise from 0.9.8 to 0.9.8.3

[Docker Debian only] Update cloudflared from 2022.4.0 to 2022.4.1

How to update? Please read this: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

Bug report: https://github.com/louislam/uptime-kuma/issues

Thank you all contributors! Bug fix, code refactoring, language files update, code review and more! @Computroniks @Saibamen @MarkusDick @mrphuongbn @kadavr95 @NixNotCastey @MrEddX
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.17 MB)
1.15.0(Apr 24, 2022)
⚠️ Change the priority of arguments (Arguments > Environment Variables) (Thanks @marcules) (It might be a breaking change for someone who set both arg and env var with different values. I guess it should be not common.)

Add new monitor type: MQTT (Thanks @tarun7singh and @chakflying)

Fix restore backup file issue.

[Status Page] Custom CSS (Thanks @patrickhafner)

[Status Page] Footer Text

[Status Page] Show/Hide Powered by Uptime Kuma

Add dropdown menu and easier to find logout button (Thanks @Computroniks and @chakflying)

Better logging format (Thanks @andreasbrett)

Add notification: OneBot (Thanks @ColdThunder11)

Add notification: PushDeer (Thanks @ngc7331)

Update Apprise to 0.9.8

Update SQLite from 3.36 to 3.38

How to update? Please read this: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

Bug report: https://github.com/louislam/uptime-kuma/issues

Thank you all contributors! Bug fix, code refactoring, language files update and code review! @fluencydoc @Alexandre-Gliganic @c0derMo @AnnAngela @MrEddX @sovushik @DX37 @PhyxionNL @koen20 @SiderealArt @mathiskir @gaby
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.16 MB)
1.15.0-beta.1(Apr 19, 2022)
⚠️ Change the priority of arguments (Arguments > Environment Variables) (Thanks @marcules) (It might be a breaking change for someone who set both arg and env var with different values. I guess it should be not common.)

Add new monitor type: MQTT (Thanks @tarun7singh @chakflying)

Fix restore backup file issue.

[Status Page] Custom CSS (Thanks @patrickhafner)

[Status Page] Footer Text

[Status Page] Show/Hide Powered by Uptime Kuma

Add dropdown menu and easier to find logout button (Thanks @Computroniks)

Better logging format (Thanks @andreasbrett)

Add notification: OneBot (Thanks @ColdThunder11)

Add notification: PushDeer (Thanks @ngc7331)

Update SQLite from 3.36 to 3.38

@fluencydoc @Alexandre-Gliganic @c0derMo @AnnAngela @MrEddX @sovushik @DX37 @PhyxionNL
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.15 MB)
1.14.1(Apr 19, 2022)
Fix Uptime Kuma 1.14.0 crashed at night (#1520)

Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.13 MB)
1.15.0-beta.0(Apr 17, 2022)
⚠️ Change the priority of arguments (Arguments > Environment Variables) (Thanks @marcules) (It might be a breaking change for someone who set both arg and env var with different values. I guess it should be not common.)

Add new monitor type: MQTT (Thanks @tarun7singh)

Fix restore backup file issue.

[Status Page] Custom CSS (Thanks @patrickhafner)

[Status Page] Footer Text

[Status Page] Show/Hide Powered by Uptime Kuma

Better logging format (Thanks @andreasbrett)

Add notification: OneBot (Thanks @ColdThunder11)

Add notification: PushDeer (Thanks @ngc7331)

@fluencydoc @Alexandre-Gliganic @c0derMo @AnnAngela @MrEddX @sovushik @DX37 @PhyxionNL
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.16 MB)
1.14.0(Apr 12, 2022)
Custom domain names for status pages

Built-in Cloudflare Tunnel supports, a super easy-to-use reverse proxy #1427 Read more...

Proxy settings for HTTP(s) Monitors #840 (Thanks @ugurerkan)

Status Page Favicon #1435 (Thanks @LoaderB0T)

Fix: Remove prometheus metrics on delete #1136

Add new language: Ukrainian (Thanks @Deni7)

Show page not found for invalid pages

Avoid some runtime deprecation warnings #1348 (Thanks @AnnAngela)

Fix Alerta issue (Thanks @Arubinu)

Fix Mattermost issue when the channel field is empty

Change SQLite to FULL synchronous mode, so it no longer corrupts the database unexpectedly.

How to update? Please read this: https://github.com/louislam/uptime-kuma/wiki/%F0%9F%86%99-How-to-Update

Bug report: https://github.com/louislam/uptime-kuma/issues

Thank you all contributors! Bug fix, code refactoring, language files update and code review! @ivanbratovic @sovushik @DX37 @BCsabaEngine @AnnAngela @JohnnyChiang

Screenshots:
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.13 MB)
1.14.0-beta.2(Apr 9, 2022)
⚠️This is BETA release. It could be unstable.

Custom domain names for status pages

Built-in Cloudflare Tunnel supports, a super easy-to-use reverse proxy #1427 Read more...

Proxy settings for HTTP(s) Monitors #840 (Thanks @ugurerkan)

Status Page Favicon #1435 (Thanks @LoaderB0T)

Fix: Remove prometheus metrics on delete #1136

Add new language: Ukrainian (Thanks @Deni7)

Show page not found for invalid pages

Avoid some runtime deprecation warnings #1348 (Thanks @AnnAngela)

Fix Alerta issue (Thanks @Arubinu)

Fix Mattermost issue when the channel field is empty

Change SQLite to FULL synchronous mode, so it no longer corrupts the database unexpectedly.

@ivanbratovic @sovushik @DX37 @BCsabaEngine @AnnAngela @JohnnyChiang
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.13 MB)
1.13.2(Apr 6, 2022)
Fix setup issue for new non-Docker users https://github.com/louislam/uptime-kuma/issues/1460

Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.09 MB)
1.14.0-beta.1(Apr 3, 2022)
⚠️This is BETA release. It could be unstable.

Built-in Cloudflare Tunnel supports, a super easy-to-use reverse proxy #1427 Read more...

Proxy settings for HTTP(s) Monitors #840 (Thanks @ugurerkan)

Status Page Favicon #1435 (Thanks @LoaderB0T)

Fix: Remove prometheus metrics on delete #1136

Add new language: Ukrainian (Thanks @Deni7)

Show page not found for invalid pages

Avoid some runtime deprecation warnings #1348 (Thanks @AnnAngela)

@ivanbratovic @sovushik @DX37 @BCsabaEngine
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.12 MB)
1.14.0-beta.0(Mar 30, 2022)
Built-in Cloudflare Tunnel supports, a super easy-to-use reverse proxy #1427 Read more...

Fix: Remove prometheus metrics on delete #1136

Show page not found for invalid pages

@ivanbratovic @sovushik @DX37
Source code(tar.gz)
Source code(zip)
dist.tar.gz(1.10 MB)