Network Management
The SolarWinds Web Console is reporting an SSL certificate mismatch in Deployment Health page
Despite trying to get the certificate set properly and despite trying to include many variants of the cn name in the cert, hostname, fqdn, and hostname*, SolarWinds is still failing in Deployment Health.
First published date
Last published date
Overview
The following warning message appears in the Deployment Health page or Active Diagnostics
"The certificate assigned to the HTTPS://URL:PORT binding does not match. The SSL certificate Issued To (CN) field does not match the server's FQDN, nor partially matches FQDN using wildcards."
The issue could happen in several cases:
1- The certificate name does not match the hostname
2- The domain name is null or empty
3- If the domain name is not empty:
3.1- For FQDN matching, the certificate name should be equal to "<host name>.<domain name>" string (using ignore case comparison)
3.2- For wildcard match, the certificate name should contain "*" symbol and should end with ".<domain name>" and should meet some additional conditions.
The certificate name may be neither FQDN nor wildcard matching (for non-empty domain name), nor an empty domain name.
Product section
Cause
This has been identified as a known issue in the SolarWinds Platform.
Resolution
This issue is addressed in SolarWinds Platform 2026.1. Consider upgrading your environment.