PDF report attachments are blank when sent by email after upgrading SolarWinds Platform

This issue can occur even though the scheduled action reports as successful. PDF exports for actions, including scheduled report emails, validate the web server certificate chain and certificate name by default. If the SolarWinds web console URL used for the export does not match the certificate CN or a SAN entry, the PDF generation may fail silently and produce a blank attachment.

The SolarWinds web console address used during PDF export does not match the certificate's Common Name (CN) or Subject Alternative Name (SAN).

For example:

• Certificate CN/SAN: https://solarwinds.company.com/

• Export URL, Website table, or web console address: https://ServerHostName.domain.local/

This mismatch can result in a CertificateCommonNameInvalid error. Starting with SolarWinds Platform 2025.2, certificate chain and name validation for PDF exports and action web-page requests is enabled by default.

Immediate workaround

1. On the SolarWinds server, open Advanced Configuration or Centralized Settings:

   https://<SolarWindsServer>/Orion/Admin/AdvancedConfiguration/Global.aspx

2. Under ExportToPdfCmd.ExportToPdfSettings, clear the following settings:

   • CheckOnCertificateChainErrors

   • CheckOnCertificateChainErrorsAndNameMismatch

3. Under SolarWinds.Orion.Core.Actions.Settings.ActionSettings, clear the following settings:

   • WebPageCheckOnCertificateNameMismatch

   • WebPageCheckOnCertificateChainErrors

4. Restart the Orion Module Engine service. This restart is required for the ActionSettings changes to take effect.

5. Manually trigger the scheduled report.

6. Confirm that the PDF attachment contains the expected report data.

Recommended permanent resolution

Update the SolarWinds web console address so that it exactly matches the certificate CN or one of its SAN entries.

1. In the SolarWinds web console, go to Settings > Web Console Settings.

2. Under SolarWinds Platform Web Server Address, specify the FQDN that matches the certificate, for example:

   https://solarwinds.company.com/

3. Apply the change.

4. Restart the Orion Module Engine service.

5. Trigger the scheduled report again and verify the PDF attachment.

Alternative database update

If the Web Console Settings cannot be changed because of a complex environment, update the website FQDN in the SolarWinds database:

1. Open Database Manager on the SolarWinds server.

2. Open the Website table in the SolarWinds database.

3. Update only the FQDN column so that it matches the certificate CN or SAN entry.

4. Do not change the ServerName column.

5. Restart the Orion Module Engine service.

6. Trigger the scheduled report again and verify the PDF attachment.

After a valid certificate is installed and the web console FQDN matches the certificate, confirm that PDF exports work successfully. The certificate validation settings can then be re-enabled.