Certificate Expiration does not display on custom ports

[crouthamela]

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

When monitoring an HTTPS URL, the Certificate Expiration countdown does not display if a custom port was specified in the URL. For example, monitoring https://myurl.com:4433 will not show the expiration date on the monitor page, but https://myurl.com will.

👟 Reproduction steps

1. Create an HTTP(s) Monitor Type
2. Enter a URL with a custom port at the end (https://myurl.com:4433)
3. Check Certificate Expiry Notification

👀 Expected behavior

Certificate Expiration date would display on the monitor page.

😓 Actual Behavior

Certificate Expiration date does not display on the monitor page.

🐻 Uptime-Kuma Version

1.20.2

💻 Operating System and Arch

Debian 11

🌐 Browser

Google Chrome 110.0.5481.105

🐋 Docker Version

No response

🟩 NodeJS Version

No response

📝 Relevant log output

No response

[chakflying]

Did a test with self-signed cert. and cannot reproduce.

[crouthamela]

Interesting. I'm having the issue with port 4433.

[CommanderStorm]

Closing as cannot-reproduce

[crouthamela]

@CommanderStorm can you try this with https://remote.vfendo.com:4433

I just upgraded to the latest Uptime Kuma to see if that made a difference, but to no avail.

[CommanderStorm]

A likely duplicate issue was triaged in #3551 and #4281 was proposed last week to fix this issue.
Said PR will be reviewed in one of the upcoming releases as we have switched to finalising v2.0