Cert Exp not shown in overview, but service marked as down when expired

[liquidat]

⚠️ 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

One out of my many tests does show the "Cert Exp." in the monitor overview - although it showed the service as DOWN when the certificate expired!

Screenshot of the service (my local FritzBox):

Screenshot of the same configuration, for my local Grafana, as comparison:

Monitor configuration:

Logs in UI, showing that the monitor was down:

Logs indicating that the expiry date was correctly identified, see below.

👟 Reproduction steps

1. Set up Kuma
2. Set up FritzBox with certificate (let's encrypt, domain based)
3. Set up Kuma monitor on FritzBox, activate "Certificate Expiry Notification"

👀 Expected behavior

The cert expiry should be shown in the monitor overview.

😓 Actual Behavior

The cert expiry is not shown.

Note that in the backed everything is working fine: when we reached the expiry date, the service was shown as down in Kuma!

🐻 Uptime-Kuma Version

1.22.1

💻 Operating System and Arch

Raspbian GNU/Linux 11 (bullseye), ARM

🌐 Browser

Chrome, Firefox

🐋 Docker Version

Docker version 20.10.5+dfsg1, build 55c4c88

🟩 NodeJS Version

16

📝 Relevant log output

uptime-kuma     | 2023-08-09T13:09:12+02:00 [MONITOR] WARN: Monitor #14 'FritzBox': Failing: certificate has expired | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
uptime-kuma     | 2023-08-09T13:10:12+02:00 [MONITOR] WARN: Monitor #14 'FritzBox': Failing: certificate has expired | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0
uptime-kuma     | 2023-08-09T13:11:12+02:00 [MONITOR] WARN: Monitor #14 'FritzBox': Failing: certificate has expired | Interval: 60 seconds | Type: http | Down Count: 0 | Resend Interval: 0

[zappityzap]

I've seen this with one of my monitors too, but haven't been able to figure out why.

[xifengzhu]

I've seen this with one of my monitors too.

[chakflying]

Would be great if someone can share a url where this is reproducible so we can test and debug this.

[xifengzhu]

Would be great if someone can share a url where this is reproducible so we can test and debug this.

https://wordmind.ai

[CommanderStorm]

@xifengzhu
Cannot reproduce; The cert is valid and is displayed as such.
The cert expiry @liquidat reported is also displayed.
Am I misssing something?

[xifengzhu]

@xifengzhu Cannot reproduce; The cert is valid and is displayed as such. The cert expiry @liquidat reported is also displayed. Am I misssing something?

I found that https://wordmind.ai can recognize the certificate, but if it is https://wordmind.ai/health_check, it cannot recognize the certificate.

[Niemand2006]

This error is when the Port from https is not 443.

[ihcops]

Would be great if someone can share a url where this is reproducible so we can test and debug this.

https://bill.vps1.net/

[ihcops]

Would be great if someone can share a url where this is reproducible so we can test and debug this.

https://bill.vps1.net/

sqlite> select * from monitor_tls_info where monitor_id=45;
17|45|{"valid":true,"certInfo":null}

[CommanderStorm]

Tested #4281 as working and fixing this example too

Details

[CommanderStorm]

Resolved in next patch release