Error generating report: Could not establish a trust relationship for SSL/TLS secure channel

Last Modified

Fri Feb 10 14:00 GMT 2023

Description

After turning on the HTTPS feature in the advanced settings, the following error occurs when generating a report:

Could not establish a trust relationship for the SSL/TLS secure channel.

Error: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel.

Or
 
The request was aborted: Could not create SSL/TLS secure channel.

Another error that may be seen is:

The underlying connection was closed: An unexpected error occurred on a receive.

Environment

  • N-able N-central
  • Report Manager

Solution

  1. Ensure the steps on how to configure HTTPS in the Report Manager installation guide have been followed. Find the corresponding Report Manager download in N-ableMe and locate the link to the Install Guide on the download page. Note that you will need to be signed in to view this information.

    OR

    https://documentation.n-able.com/N-central/troubleshooting/Content/kb/Configure-HTTPS-and-SSL-for-Report-Manager.htm

  2. The most common mistake is setting the Server IP Configuration > Internal IP Address to an IP Address instead of the FQDN.

  3. Open IE as Administrator and Test Browsing to: 
    • https://<FQDN of the RM server here>/Reports
    • If prompted for username and password, click the checkbox next to Remember.
  4. Ensure the FQDN resolves correctly, both internally and externally.

    Example:
    From the command line, the Report Manager Server FQDN should properly resolve to the internal IP address internally, and the external address externally.
    Here we see the FQDN properly resolves internally to an internal IP address.

    5. # nslookup reports.mycompany.com

    Server: 192.168.1.1

    Address: 192.168.1.1#53



    Non-authoritative answer:

    reports.mycompany.com canonical name = reports.mycompany.com.

    Name: reports.mycompany.com

    Address: 192.168.4.20

  5. The certificate is not a valid certificate signed by a CA. Reporting Services has strict requirements on the certificate and it must be valid.
  6. The certificate has not been added to the SQL Server reporting services settings.
    • To do this, open SQL Server Reporting Services Configuration Manager and ensure you add the certificate to both the Web service URL and Report Manager URL.
  7. Try rebuilding the Reportserver virtual directories using SSRS Config Manager.
    1. Check that each of the IP Addresses are set to All Assigned: 
      • Click Webservice URL > check IP Address is set to All Assigned.
      • Click Report Manager URL > Advanced >check IP Address is set to All Assigned.
    2. Change Webservice URL to ReportServer1 > Apply > change back to ReportServer > Apply.
    3. Change Report Manager URL to Reports1 > apply > change to Reports > Apply.
  8. Check no hostname specified in Bindings.
    1. Open Internet Information Server Configuration Manager.
    2. Expand ServerName > Sites > right-click Default Web Site > Edit Bindings.
    3. Select the HTTPS binding then click Edit and ensure there is no hostname specified.
  9. If https://FQDN_HERE/Reports is not loading, refer the partner to attempt the steps on this link and then reinstall Report Manager if successful.
    Example: 
    The Microsoft SSRS Reports page should load successfully using FQDN. https://reports.mycompany.com/Reports
  10. If you have tried all of the above, be sure to attempt a reinstall of Report Manager before contacting N-able Technical Support.