starred/uptime-kuma

Fork 0

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

Feature Request - Minimum TLS version check (e.g. enforce a minimum of TLS 1.2) #4013

New issue

Open

opened 2026-02-28 03:48:12 -05:00 by deekerman · 5 comments

deekerman commented

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

Owner

Originally created by @ndbroadbent on GitHub (Mar 3, 2025).

Couldn't find any related issues

🏷️ Feature Request Type

New monitor

🔖 Feature description

It would be great if we could set up an SSL check that verifies certificates and also configures a minimum TLS version, e.g. 1.0, 1.1, 1.2, or 1.3.

1.0 and 1.1 are legacy TLS versions, so I'd like to set up checks for all of my domains and make sure I don't accidentally support them. Thanks!

✔️ Solution

New SSL monitor for minimum TLS version

❓ Alternatives

Couldn't find any, maybe a bash script as a cron job

📝 Additional Context

No response

Originally created by @ndbroadbent on GitHub (Mar 3, 2025). ### 📑 I have found these related issues/pull requests Couldn't find any related issues ### 🏷️ Feature Request Type New monitor ### 🔖 Feature description It would be great if we could set up an SSL check that verifies certificates and also configures a minimum TLS version, e.g. 1.0, 1.1, 1.2, or 1.3. 1.0 and 1.1 are legacy TLS versions, so I'd like to set up checks for all of my domains and make sure I don't accidentally support them. Thanks! ### ✔️ Solution New SSL monitor for minimum TLS version ### ❓ Alternatives Couldn't find any, maybe a bash script as a cron job ### 📝 Additional Context _No response_

deekerman added the

feature-request

A:monitor

type:new

labels

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

deekerman commented

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

Author

Owner

@Ghost93 commented on GitHub (Mar 26, 2025):

interested 👍

@Ghost93 commented on GitHub (Mar 26, 2025): interested 👍

deekerman commented

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

Author

Owner

@CommanderStorm commented on GitHub (Apr 17, 2025):

Maybe relevant for some: that we currently support the tls versions that node supports by default.

@CommanderStorm commented on GitHub (Apr 17, 2025): Maybe relevant for some: that we currently support the tls versions that node supports by default.

deekerman commented

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

Author

Owner

@jnovack commented on GitHub (May 3, 2025):

Forgive me, why is checking for TLS 1.1 the responsibility of the uptime checker checking every X minutes?

Ignoring that security scans are the responsibility of the network security tool (which this is not), how often is someone accidentally enabling TLS 1.1 that you need to have it checked EVERY time you check to see if the host is up?

I feel this is scope creep at it's worst.

@jnovack commented on GitHub (May 3, 2025): Forgive me, why is checking for TLS 1.1 the responsibility of the uptime checker checking every X minutes? Ignoring that security scans are the responsibility of the network security tool (which this is not), how often is someone accidentally enabling TLS 1.1 that you need to have it checked EVERY time you check to see if the host is up? I feel this is scope creep at it's worst.

deekerman commented

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

Author

Owner

@Loughty commented on GitHub (Aug 6, 2025):

Maybe relevant for some: that we currently support the tls versions that node supports by default.

Hi @CommanderStorm, there's a way of lowering the min TLS version supported? (has u can do, for example, in Firefox). After an update, my Uptime Kuma now show one host has down, and the "ignoring TLS/SSL errors" option isn't working this time. I think it's because the min TLS version supported has ben raised (I update Uptime Kuma from 1.19 to 1.23).

@Loughty commented on GitHub (Aug 6, 2025): > Maybe relevant for some: that we currently support the tls versions that node supports by default. Hi @CommanderStorm, there's a way of lowering the min TLS version supported? (has u can do, for example, in Firefox). After an update, my Uptime Kuma now show one host has down, and the "ignoring TLS/SSL errors" option isn't working this time. I think it's because the min TLS version supported has ben raised (I update Uptime Kuma from 1.19 to 1.23).

deekerman commented

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

Author

Owner

@CommanderStorm commented on GitHub (Aug 6, 2025):

Yes, just pass the relevant node environment variables.

Please fix your services instead of bodging like this though.

@CommanderStorm commented on GitHub (Aug 6, 2025): Yes, just pass the relevant node environment variables. Please fix your services instead of bodging like this though.