TSL certificate error

[Lihy6472]

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

• I checked and didn't find similar issue

🛡️ Security Policy

• I agree to have read this project Security Policy

📝 Describe your problem

Error dialling a https address

📝 Error Message(s) or Log

write EPROTO C087507E347F0000:error:0A000172:SSL routines:tls12_check_peer_sigalg:wrong signature type:../deps/openssl/openssl/ssl/t1_lib.c:1594:

Time (Asia/Shanghai): 2024-05-22 09:01:10

🐻 Uptime-Kuma Version

1.23.10

💻 Operating System and Arch

Debian GNU/Linux 10 (buster)

🌐 Browser

124.0.6367.92

🖥️ Deployment Environment

docker deployment

[Lihy6472]

• uptime-kuma

• curl

• After configuring Chromium, it can be used normally, but the certificate expiration time cannot be detected

[CommanderStorm]

What do you mean by configuring chromium?

[Lihy6472]

What does it mean to configure Chromium?

[CommanderStorm]

can you please update to 1.23.13?
We have made some improvements in this area in the last patch-releases.

[Lihy6472]

你能更新到吗1.23.13？ 我们在最近的补丁版本中对此领域做了一些改进。

• I am already in version 1.23.13 now

• The same domain name,The request "1" cannot be successfully made using the HTTPS method,
• "拨测"Using Chromium allows for normal requests

[CommanderStorm]

What do you mean by cannot be monitored using https?
Can you share the URL of what you are trying to monitor? (This is really hard to remote debug)

Could you please also try if using uptime.kuma.pet experiences the same behaviour?

[Lihy6472]

无法使用 https 监控是什么意思？ 您可以分享您要监控的 URL 吗？（这对于远程调试来说确实很困难）

您是否可以尝试使用 uptime.kuma.pet 是否会出现同样的行为？

• The following errors may occur when using HTTPS。

2024-05-27T09:00:50+08:00 [MONITOR] WARN: Monitor #3 '1': Failing: write EPROTO C047C726837F0000:error:0A000172:SSL routines:tls12_check_peer_sigalg:wrong signature type:../deps/openssl/openssl/ssl/t1_lib.c:1594:
 | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0