Incorrect Cert Expiry Time

[inthenightsky]

📑 I have found these related issues/pull requests

N/A

🛡️ Security Policy

• I agree to have read this project Security Policy

Description

The SSL certificate for my site has renewed for a year, but this isn't reflected on the monitor.

👟 Reproduction steps

I'm unsure on exact reproduction steps, but:

• create a new monitor
• make a change to the SSL cert (?)
• observe the information related to the cert (expiry date, days remaining) don't update when the monitor refreshes

👀 Expected behavior

The correct information related to the cert should be grabbed and used instead.

😓 Actual Behavior

An incorrect expiry date & days remaining are displayed.

🐻 Uptime-Kuma Version

1.23.11

💻 Operating System and Arch

Ubuntu 20.04.6 LTS x64

🌐 Browser

Firefox 123.0.1

🖥️ Deployment Environment

• Runtime: Docker version 25.0.3
• Database: Local SQLite
• Filesystem used to store the database on: Linux ext4 on an SSD
• number of monitors: 3

📝 Relevant log output

No response

[CommanderStorm]

I cannot confirm this problem on my device.

Let's debug this to find what is different:

• are you using the dashboard or the status page?
• What happens when you reload the page?

@chakflying what do you think:
Could this be related to #4281

[inthenightsky]

Thanks for the reply. I'm just using the dashboard, and behaviour is consistent through refreshes and even on another browser.

[CommanderStorm]

What happens when you click on this tab in the dashboard? (yould you post a screenshot?)

[inthenightsky]

Sure,

I've removed the domain name & fingerprint to maintain my privacy, but I'll drop you an email directly with the domain name so you can see it's SSL info.

[CommanderStorm]

I think I have a good hint.

When was the last time a ping was executed (we don't support floats as latency => the last ping latency was 4,4 days???).
Am I reading something wrong here?

[CommanderStorm]

What monitor are you using?

[inthenightsky]

Pings are executing every 60s.

The monitor is HTTP(s) using the Chromium browser engine.

[CommanderStorm]

What do you get when hovering over the last ping

Are there any events? (Listed below)

[inthenightsky]

There are events, but these relate to the previous monitor type - it was swapped from standard to the Chromium engine a while ago. These don't seem to reflect reality since there's no keyword check option with the Chromium engine type.

[inthenightsky]

A small troubleshooting step I just performed was creating a new monitor again using the Chromium engine type, this time cert expiry stats aren't reported.

New Monitor:

Old Monitor:

I think when the monitor type was swapped something funky went down.

[CommanderStorm]

I am a bit unsure if this is caused by #4281 or if real-browser need investigating.

Currently, I don't think investigating the second option is worth active consideration given that #4281 is not merged + released.
=> I have changed this to an help issue, as I think looking at this next release is more productive ^^

[github-actions]

We are clearing up our old help-issues and your issue has been open for 60 days with no activity.
If no comment is made and the stale label is not removed, this issue will be closed in 7 days.