Symptoms

We got a certificate for our staging environment (K2Staging.denallix.com), but still saw an error in production (K2.denallix.com) using the same certificate.
 

Diagnoses

The K2Staging.denallix.com certificate was created specifically for the staging environment and will not work in production (K2.denallix.com) as well. I instructed the client to try and get a wildcard certificate that will work with *.denallix.com.

I was informed that they had a certificate for K2.denallix.com as well, however, when they enter the runtime URL in production, they get redirected to servername.denallix.com and this caused a mismatch of names for SSL.
 

Resolution

After looking at the site in IIS, we noticed that there were no host headers configured for K2.denallix.com and K2stg.denallix.com on the sites in IIS.

We proceeded to create bindings for K2.denallix.com in production and K2Staging.denallix.com in their respective environments and re-configured blackpearl to use the newly created bindings.