Expiration certificat notification on status page #3135

Open
opened 2026-02-28 03:19:17 -05:00 by deekerman · 1 comment
Owner

Originally created by @Lurikbolding on GitHub (Feb 20, 2024).

I have not found same issue

🛡️ Security Policy

Description

A create about 20 Monitors.
I add all monitor on a status page.
Some monitor have "Certificate Expiry Notification" parameter
Some have not "Certificate Expiry Notification".

But on status page, some monitor WITHOUT the "Certificate Expiry Notification" show the remaing time for the certificat.
up1
up2

👟 Reproduction steps

I'm not sure how to reproduce, but the monitor has been create by clone an existing monitor with the "Certificate Expiry Notification" check to ON.
Then after the clone, i uncheck the "Certificate Expiry Notification", but it is still visible on status page.

👀 Expected behavior

the "expiration cert" info on the status page follow the setting "Certificate Expiry Notification" of the monirot

😓 Actual Behavior

Some monitor have always the information about expiration cert visible

🐻 Uptime-Kuma Version

Version: 1.23.11 Frontend Version: 1.23.11

💻 Operating System and Arch

Docker on Synology DSM 7.2 (busybox)

🌐 Browser

Firefox 122.0.1

🖥️ Deployment Environment

  • Runtime: docker 20.10.23 build 876964a
  • Database: embedded ?
  • Filesystem used to store the database on: btrfs on the NAS
  • number of monitors: 20

📝 Relevant log output

Update the monitor and just after

date	stream	content
2024/02/20 12:48:04	stderr	2024-02-20T12:48:04+01:00 [MONITOR] ERROR: res.request.res.socket.getPeerCertificate is not a function
2024/02/20 12:48:04	stderr	2024-02-20T12:48:04+01:00 [MONITOR] ERROR: Caught error
2024/02/20 12:48:02	stdout	2024-02-20T12:48:02+01:00 [MONITOR] INFO: Get Monitor: 17 User ID: 1
2024/02/20 12:48:02	stdout	2024-02-20T12:48:02+01:00 [MANAGE] INFO: Resume Monitor: 17 User ID: 1
Originally created by @Lurikbolding on GitHub (Feb 20, 2024). ### 📑 I have found these related issues/pull requests I have not found same issue ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description A create about 20 Monitors. I add all monitor on a status page. Some monitor have "Certificate Expiry Notification" parameter Some have not "Certificate Expiry Notification". But on status page, some monitor WITHOUT the "Certificate Expiry Notification" show the remaing time for the certificat. ![up1](https://github.com/louislam/uptime-kuma/assets/45403655/cd8e2e55-fdec-4c93-bc70-fffa59c11e58) ![up2](https://github.com/louislam/uptime-kuma/assets/45403655/217c04a8-31d1-4478-8288-03561c957705) ### 👟 Reproduction steps I'm not sure how to reproduce, but the monitor has been create by clone an existing monitor with the "Certificate Expiry Notification" check to ON. Then after the clone, i uncheck the "Certificate Expiry Notification", but it is still visible on status page. ### 👀 Expected behavior the "expiration cert" info on the status page follow the setting "Certificate Expiry Notification" of the monirot ### 😓 Actual Behavior Some monitor have always the information about expiration cert visible ### 🐻 Uptime-Kuma Version Version: 1.23.11 Frontend Version: 1.23.11 ### 💻 Operating System and Arch Docker on Synology DSM 7.2 (busybox) ### 🌐 Browser Firefox 122.0.1 ### 🖥️ Deployment Environment - Runtime: docker 20.10.23 build 876964a - Database: embedded ? - Filesystem used to store the database on: btrfs on the NAS - number of monitors: 20 ### 📝 Relevant log output ```shell Update the monitor and just after date stream content 2024/02/20 12:48:04 stderr 2024-02-20T12:48:04+01:00 [MONITOR] ERROR: res.request.res.socket.getPeerCertificate is not a function 2024/02/20 12:48:04 stderr 2024-02-20T12:48:04+01:00 [MONITOR] ERROR: Caught error 2024/02/20 12:48:02 stdout 2024-02-20T12:48:02+01:00 [MONITOR] INFO: Get Monitor: 17 User ID: 1 2024/02/20 12:48:02 stdout 2024-02-20T12:48:02+01:00 [MANAGE] INFO: Resume Monitor: 17 User ID: 1 ```
Author
Owner

@CommanderStorm commented on GitHub (Feb 20, 2024):

Related https://github.com/louislam/uptime-kuma/issues/3615

@CommanderStorm commented on GitHub (Feb 20, 2024): Related https://github.com/louislam/uptime-kuma/issues/3615
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/uptime-kuma#3135
No description provided.