Website configuration failed due to SSL certificate mismatch on HTTPS binding

When running the SolarWinds Configuration Wizard on the main polling engine, the Website step fails with “Website configuration failed” and the web console cannot be opened over HTTPS. The Check site certificates diagnostic reports that the SSL certificate bound to the SolarWinds website in IIS does not match what SolarWinds expects on the configured HTTPS binding (for example, https://<server>:8787).

The SSL certificate bound to the SolarWinds website’s HTTPS binding in IIS (for example, IP 192.168.1.56 on port 8787) does not match the certificate that SolarWinds expects, as detected by the Check site certificates diagnostic. As a result, the Website configuration step in the Configuration Wizard fails and the web console cannot be reached over HTTPS.

1. Confirm the current HTTPS binding in IIS

   1. Open IIS Manager on the SolarWinds main polling engine.

   2. In the left pane, expand Sites and select the SolarWinds Platform (or SolarWinds Orion) website.

   3. In the Actions pane, select Bindings….

   4. Locate the https binding used by SolarWinds (for example, IP 192.168.30.56, port 8787).

   5. Select the binding and click Edit….

   6. Note the IP address, Port, and especially the SSL certificate currently selected. This is the binding that the diagnostic reports as having the wrong certificate.

2. Verify that the correct certificate exists and is valid

   1. On the SolarWinds server, run mmc.exe.

   2. Add the Certificates snap-in for the Computer account.

   3. In Certificates (Local Computer), expand Personal → Certificates.

   4. Locate the intended SolarWinds Platform certificate (for example, with a friendly name matching your SolarWinds site FQDN or SolarWinds-Orion).

   5. Confirm that:

      • The certificate is not expired.

      • It has a private key.

      • The certificate chain is trusted (no errors when you open it).

   6. If the correct certificate is missing or invalid, either:

      • Import the correct certificate (with private key) into Local Computer → Personal, or

      • Plan to let the Configuration Wizard create a new self-signed certificate and use that certificate for the SolarWinds website binding.

3. Re-bind the correct certificate to the HTTPS binding in IIS

   1. Return to IIS Manager → Sites → SolarWinds Platform website → Bindings… → Edit for the HTTPS binding.

   2. In SSL certificate, choose the correct, valid certificate from Local Computer → Personal.

   3. Click OK to save the binding.

   4. Ensure there is only one active HTTPS binding for the SolarWinds website on the expected IP and port combination (for example, IP 192.168.30.56, port 8787). This aligns the IIS binding with what the diagnostic expects and removes the certificate mismatch condition.

4. Re-run the Configuration Wizard and complete the Website step

   1. On the main polling engine, run the SolarWinds Configuration Wizard as an elevated administrator.

   2. Proceed through the Database and Services steps as normal.

   3. On the Website step:

      • Confirm that the site is configured to use HTTPS on the expected port (for example, 8787).

      • If prompted for a certificate, select the same certificate you just bound in IIS.

   4. Let the Configuration Wizard complete the Website configuration.

   5. After the wizard finishes successfully, browse to the SolarWinds web console URL (for example, https://<server>:8787/Orion/Login.aspx) and confirm that it loads without a Website configuration failed error.

Additional Notes:

• If your environment uses a certificate issued by an internal or public CA, ensure the full chain (root and any intermediate CAs) is trusted on the SolarWinds server before binding the certificate in IIS.

• If you allow the Configuration Wizard to generate a self-signed certificate, plan to replace it later with a production certificate that meets your organization’s security requirements.