JHP

Just wanted to confirm that this is now fixed, and we're using it in production!
 
Thanks!

Could you please email our support with the real hostnames so we can try to reproduce? 
Thank you.
Thank you Jakob,
we have added this issue to be fixed for the next agent release.

We have received the email and managed to reproduce the issue. A fix will be included in the next release.
Thank you for your help!
Marius

I too have experienced this (or a similar) issue, but with SAN type of certificates.
Given a SAN certificate with the following hostnames (in this order):
*.domain1.com
*.domain2.com
And an certificate monitor setup for foo.domain2.com - I indeed see the number of days until expiry, but a result that says something like "certificate cannot be verified".
If I change the monitor to check for something like foo.domain1.com (the first domain on the cert) - everything goes green and works as expected. I'm guessing that it only works properly when verifying the first hostname on the certificate or something?
For reference, I'm running on Windows 2008R2 (with the latest version of the Pulseway agent).
Hope this helps -- let me know if I can provide any further details!
 

Hi,
 
Welcome to the Pulseway community. Please PM me the hostname and port of the service that uses the wildcard certificate (if it's in the DMZ) and we will investigate the issue.
 
Regards,
Chris
Pulseway Support