Limit frequency of certificate expiration alerts #3780

Open
opened 2026-02-28 03:40:45 -05:00 by deekerman · 0 comments
Owner

Originally created by @suominen on GitHub (Nov 24, 2024).

I did not find any related issues.

🛡️ Security Policy

Description

CDN-like systems can take time to roll out a new certificate to all nodes. During the roll-out window, Kuma will issue lots of notifications if it is alternately connecting to a node with the old certificate and to a node with the new certificate, if the old certificate is within the expiry notification window.

👟 Reproduction steps

Set up a site with e.g. Webflow, who roll out new LE certificates only after the remaining lifetime of the certificate is less than 14 days.

👀 Expected behavior

Notify at most once per day about certificate expiration.

😓 Actual Behavior

You may get notifications as frequently as every 2 minutes for a 60-second monitor. The frequency diminishes as the new certificate gets installed on more nodes.

🐻 Uptime-Kuma Version

1.23.15

💻 Operating System and Arch

Debian 12.8

🌐 Browser

N/A

🖥️ Deployment Environment

  • Runtime: Docker 27.3.1
  • Database: sqlite
  • Filesystem used to store the database on: xfs
  • number of monitors: 7

📝 Relevant log output

No response

Originally created by @suominen on GitHub (Nov 24, 2024). ### 📑 I have found these related issues/pull requests I did not find any related issues. ### 🛡️ Security Policy - [X] I agree to have read this project [Security Policy](https://github.com/louislam/uptime-kuma/security/policy) ### Description CDN-like systems can take time to roll out a new certificate to all nodes. During the roll-out window, Kuma will issue lots of notifications if it is alternately connecting to a node with the old certificate and to a node with the new certificate, if the old certificate is within the expiry notification window. ### 👟 Reproduction steps Set up a site with e.g. Webflow, who roll out new LE certificates only after the remaining lifetime of the certificate is less than 14 days. ### 👀 Expected behavior Notify at most once per day about certificate expiration. ### 😓 Actual Behavior You may get notifications as frequently as every 2 minutes for a 60-second monitor. The frequency diminishes as the new certificate gets installed on more nodes. ### 🐻 Uptime-Kuma Version 1.23.15 ### 💻 Operating System and Arch Debian 12.8 ### 🌐 Browser N/A ### 🖥️ Deployment Environment - Runtime: Docker 27.3.1 - Database: sqlite - Filesystem used to store the database on: xfs - number of monitors: 7 ### 📝 Relevant log output _No response_
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#3780
No description provided.