JHP Posted July 10, 2015 Posted July 10, 2015 We are trying to set up SSL certificate monitoring, and it's working fine for our standard certificates, e.g. test.company.com and prod.company.com. When viewing the certificates in the app we get the number of days left before expiration. So far so good. However, as soon as we add our wildcard certificate, *.company.com, to the configuration, the "Certificates" page for the server in the app just shows "Loading monitored certificates...", eventually yielding "Data not available." As soon as the wildcard certificate is removed from the config, we can view the others just fine.
Staff Chris Posted July 10, 2015 Staff Posted July 10, 2015 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 JHP 1
JHP Posted July 13, 2015 Author Posted July 13, 2015 I've PM'ed you the details - thanks for looking in to this!
JHP Posted August 3, 2015 Author Posted August 3, 2015 Have your engineers been able to reproduce the issue?
Marius Posted August 4, 2015 Posted August 4, 2015 What server address are you entering when adding the certificate entry in Pulseway Manager?Can you please email our support with the details?
Marius Posted August 18, 2015 Posted August 18, 2015 We're still trying to reproduce this. Is the problem happening on the Windows, Linux or Mac agent?
JHP Posted August 20, 2015 Author Posted August 20, 2015 Hi MariusThe error is present on a Linux agent, running on Ubuntu Server 14.04.Prompted by your question I just tried setting up a Windows agent on a desktop machine and adding cert monitoring - on Windows the wildcard certificate monitoring works fine!/Jakob
Dan P. Posted August 31, 2015 Posted August 31, 2015 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.comAnd 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! JHP 1
Marius Posted September 1, 2015 Posted September 1, 2015 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.comAnd 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! Could you please email our support with the real hostnames so we can try to reproduce? Thank you. Hi MariusThe error is present on a Linux agent, running on Ubuntu Server 14.04.Prompted by your question I just tried setting up a Windows agent on a desktop machine and adding cert monitoring - on Windows the wildcard certificate monitoring works fine!/JakobThank you Jakob,we have added this issue to be fixed for the next agent release. JHP 1
Dan P. Posted September 1, 2015 Posted September 1, 2015 Marius,I've emailed in exact repro details to support.
Marius Posted September 1, 2015 Posted September 1, 2015 Marius,I've emailed in exact repro details to support.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 JHP 1
JHP Posted September 30, 2015 Author Posted September 30, 2015 Just wanted to confirm that this is now fixed, and we're using it in production! Thanks! Chris 1
Marius Posted October 5, 2015 Posted October 5, 2015 Thank you for the update and for your support on this, glad it is working well.
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now