starred/uptime-kuma

Fork 0

mirror of https://github.com/louislam/uptime-kuma.git synced 2026-03-02 22:57:00 -05:00

Monitors with `Ignore TLS/SSL error` enabled show up as expired in the `/metrics` #970

New issue

Open

opened 2026-02-28 02:05:45 -05:00 by deekerman · 1 comment

deekerman commented

2026-02-28 02:05:45 -05:00

Owner

Originally created by @sniff122 on GitHub (Apr 11, 2022).

⚠️ Please verify that this bug has NOT been raised before.

I checked and didn't find similar issue

🛡️ Security Policy

I agree to have read this project Security Policy

Description

Ive noticed in the metrics page that can be used with prometheus, HTTPS servers that dont have a valid signed (but still in date) certificate are displayed as expired despite having Ignore TLS/SSL error for HTTPS websites enabled in the advanced section of the monitor.

Additionally, ive noticed that monitors that use the push type display as down too (see attached screenshots for both)

Im not sure if this is intended behaviour or not, which is why im making this issue

Im using the latest nightly build with docker (1.13.1-nightly)

Monitor using push showing as up in the web UI:

Monitor showing as down in the /metrics page:

Monitor with a self signed/unknown CA certificate showing as not expired and displaying the expiry date in the web UI:

Monitor with a self signed/unknown CA certificate showing as expired but still displaying the expiry date on the stats page:
![Monitor with a self signed/unknown CA certificate showing as expired](https://lewisthe.computer/uploads
/1ec7805038b63ff3f0af.png)

👟 Reproduction steps

Add a HTTPS monitor using a self signed certificate making sure that the Ignore TLS/SSL error for HTTPS websites is enabled and it should say as up and have the certificate expiry time. When looking at the /metrics page it will show as expired (0) but still have the expiry date

For the push monitor, add one and ensure that its being pushed to and showing up in the web UI but in /metrics it will show as down (0)

👀 Expected behavior

The certificate info will respect the Ignore TLS/SSL error for HTTPS websites option for the monitor in the /metrics page and display the same info as the web UI

The push monitor should follow the status in the web UI (up or down)

😓 Actual Behavior

For self signed/unknown CA certificates the monitor displays as expired in /metrics but valid in the web UI but still displays the expiry date

For push monitors, the monitor is displayed as down in /metrics and up on the web UI

🐻 Uptime-Kuma Version

1.13.1-nightly

💻 Operating System and Arch

Ubuntu 18.04.6 LTS x86_64

🌐 Browser

Firefox v99 (64 bit) on ubuntu 21.10

🐋 Docker Version

Docker version 20.10.7, build 20.10.7-0ubuntu5~18.04.3

🟩 NodeJS Version

No response

📝 Relevant log output

No response

Originally created by @sniff122 on GitHub (Apr 11, 2022). ### ⚠️ 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](https://github.com/louislam/uptime-kuma/security/policy) ### Description Ive noticed in the metrics page that can be used with prometheus, HTTPS servers that dont have a valid signed (but still in date) certificate are displayed as expired despite having `Ignore TLS/SSL error for HTTPS websites` enabled in the advanced section of the monitor. Additionally, ive noticed that monitors that use the `push` type display as down too (see attached screenshots for both) Im not sure if this is intended behaviour or not, which is why im making this issue Im using the latest nightly build with docker (1.13.1-nightly) Monitor using push showing as up in the web UI: ![Monitor using the push type showing as up in the web UI](https://lewisthe.computer/uploads/599fae87db8fd7dc2280.png) Monitor showing as down in the /metrics page: ![Monitor using the push type showing as down in the metrics page](https://lewisthe.computer/uploads/4a2980aa96bae59e7064.png) Monitor with a self signed/unknown CA certificate showing as not expired and displaying the expiry date in the web UI: ![Monitor with a self signed/unknown CA certificate showing as not expired and displaying the expiry date in the web UI](https://lewisthe.computer/uploads/41d788db3ebc4999419c.png) Monitor with a self signed/unknown CA certificate showing as expired but still displaying the expiry date on the stats page: ![Monitor with a self signed/unknown CA certificate showing as expired](https://lewisthe.computer/uploads /1ec7805038b63ff3f0af.png) ![Monitor with a self signed/unknown CA certificate showing expiry date](https://lewisthe.computer/uploads/e18f6d67bfe054fab483.png) ### 👟 Reproduction steps Add a HTTPS monitor using a self signed certificate making sure that the `Ignore TLS/SSL error for HTTPS websites` is enabled and it should say as up and have the certificate expiry time. When looking at the /metrics page it will show as expired (0) but still have the expiry date For the push monitor, add one and ensure that its being pushed to and showing up in the web UI but in /metrics it will show as down (0) ### 👀 Expected behavior The certificate info will respect the `Ignore TLS/SSL error for HTTPS websites` option for the monitor in the /metrics page and display the same info as the web UI The push monitor should follow the status in the web UI (up or down) ### 😓 Actual Behavior For self signed/unknown CA certificates the monitor displays as expired in /metrics but valid in the web UI but still displays the expiry date For push monitors, the monitor is displayed as down in /metrics and up on the web UI ### 🐻 Uptime-Kuma Version 1.13.1-nightly ### 💻 Operating System and Arch Ubuntu 18.04.6 LTS x86_64 ### 🌐 Browser Firefox v99 (64 bit) on ubuntu 21.10 ### 🐋 Docker Version Docker version 20.10.7, build 20.10.7-0ubuntu5~18.04.3 ### 🟩 NodeJS Version _No response_ ### 📝 Relevant log output _No response_

deekerman added the

bug

A:metrics

labels

2026-02-28 02:05:45 -05:00

deekerman commented

2026-02-28 02:05:48 -05:00

Author

Owner

@RubenNL commented on GitHub (Dec 27, 2022):

I am having the same problem. Have you found a workaround? If not, I will try solving this one in the near future.

EDIT: actually, for me its a bit different. It shows when its down, but when its back up its gone from the metrics page.

@RubenNL commented on GitHub (Dec 27, 2022): I am having the same problem. Have you found a workaround? If not, I will try solving this one in the near future. EDIT: actually, for me its a bit different. It shows when its down, but when its back up its gone from the metrics page.