ERR_HTTP2_PROTOCOL_ERROR only for /ReportServer URL but not for /Reports URL

JohnSebastian-3934 546 Reputation points
2023-03-22T22:43:47.0466667+00:00

I have a wildcard cert stored in the Certs database on my Windows 2022 Data Center host.

I configured SQL Server Reporting Services 2017 so that both the Web Service URL and Web Portal URL have the wildcard cert connected and port 443 is specified for All IPv4.

Here is the configuration for the Web Service URL:

User's image

Here is the configuration for the Web Portal URL:

User's image

If I then use the https://hostname.nwm.doe.gov/Reports URL, it all works however if I use the https://hostname.nwm.doe.gov/ReportServer URL, I get this error:

User's image

Clicking on the i to the left of the URL gives this information:

This site does not have a certificate.

plus some additional information about security.

Can anyone give me a hint on why the /ReportServer virtual directory doesn't see the certificate?

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
0 comments No comments
{count} votes

3 answers

Sort by: Most helpful
  1. Anonymous
    2023-03-23T01:33:53.0666667+00:00

    Hi @JohnSebastian-3934

    I don't know if your specific configuration steps are correct. If you have installed the certificate correctly, when configuring the web service URL, you only need to select the friendly name of the certificate you created earlier in the "HTTPS certificate" drop-down list and click the "Apply" button.

    For more details, you can refer to this link: https://askgarth.com/blog/how-to-setup-ssrs-to-use-https-part-2/.

    If the answer is helpful, please click Accept Answer and Up-Vote for the same. If you have any questions, please feel free to let me know.

    Best regards,

    Aniya


  2. Anonymous
    2023-06-12T11:24:19.5066667+00:00

    Hello, I have the same issue with a certificate coming from our internal PKI. So it's not related to the wildcard.

    Something found the solution?

    0 comments No comments

  3. Aslan Patchagulov 0 Reputation points
    2024-08-15T06:58:08.6166667+00:00

    Disabling HTTP/2 on the server helped me to solve this problem.

    Just create two keys EnableHttp2Tls, EnableHttp2Cleartext in regedit and set them 0. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP\Parameters

    0 comments No comments

Your answer

Answers can be marked as 'Accepted' by the question author and 'Recommended' by moderators, which helps users know the answer solved the author's problem.