Network Management

After upgrading to 2026.1, all reports appear blank with the error message: “A connection attempt timed out.”

After upgrading to 2026.1, reports appear blank with the error message: “A connection attempt timed out.”

First published date

2/18/2026 3:11 PM

Last published date

2/18/2026 3:11 PM

Overview

 After upgrading to 2026.1, reports appear blank with the error message: “A connection attempt timed out.”

Product section

Network Performance Monitor

Cause

This confirms that the issue is related to the SSL/TLS certificate configuration on the SolarWinds web server rather than the report itself. When SolarWinds attempts to access:

https://<SolarWids Server>:443/Orion/Report.aspx?ReportID=1319

the connection fails because the certificate presented by the server is either untrusted or invalid.

Resolution

To resolve this issue, please have your Windows/IIS team review and address the following on the SolarWinds Platform server:

1. Validate the HTTPS Certificate

  • From the SolarWinds server, open https://<SolarWinds Server> (or the FQDN normally used).

  • Confirm that:

    • The certificate is not expired.

    • The CN/SAN matches the hostname used in the URL.

    • The certificate chain (root and intermediate CAs) is trusted by the server.

2. Verify the IIS HTTPS Binding

  • Open IIS Manager.

  • Navigate to Sites → [SolarWinds Platform site] → Bindings…

  • Select the https:443 binding → Click Edit.

  • Ensure a valid, trusted certificate is selected that corresponds to the hostname in use.

3. Install Missing CA Certificates (If Using an Internal CA)

If the certificate is issued by an internal enterprise CA, ensure that the root and intermediate CA certificates are installed in the Local Computer certificate store under:

  • Trusted Root Certification Authorities

  • Intermediate Certification Authorities

4. Retest the Scheduled Report

  • After updating the certificate and IIS binding, restart IIS and SolarWinds services as required.

  • Re-run the scheduled report and confirm:

    • No SSL/TLS errors appear in the Action Execution log.

    • The PDF/Excel report is generated successfully and opens without “connection attempt timed out” errors.

Once the SSL/TLS configuration is corrected and trusted, scheduled reports should function as expected.