SSRS URL not accessible Locally via SSL

Question

I am testing SSL Certs on a SQL 2014 express standalone version getting ready for a MBAM 2.5sp1 install..  I have configured the SQL services configured on the SQL server to be forced to SSL communication.  Now on SSRS, I am getting SSL cert RC4 warnings on the SSL links locally on the server only. When I connect to the SSL links Https://server.mydomain.com/Reports or ReportServer I get this error "This page can’t be displayed -- Turn on TLS 1.0, TLS 1.1, and TLS 1.2 in Advanced settings and try connecting to https://server.mydomain.com again. If this error persists, it is possible that this site uses an unsupported protocol or cipher suite such as RC4 (link for the details), which is not considered secure. Please contact your site administrator."  When I connect to this link from another computer it works as expected without the warning.  I can't finish the SSRS portion of MBAM because it can't connect to these links locally when I am installing it.  I get a security warning when I install firefox locally on the server too, so using a different browser.  I am testing with a 90 day free SSL cert from Comodo before I buy one.  Can anyone tell me if this behavior is normal?  I created the cert from a CSR like in this youtube video, https://www.youtube.com/watch?v=GyDwuYKXjB8 .  Is there a way to get these SSL links to work on the server locally as they do remotely or from another computer?

Answer 1

Hi Ryan,

Are able to create binding of certificate ?

share error .Refer following link

http://stackoverflow.com/questions/34372139/configure-ssrs-for-ssl

---

Please click Mark As Answer if my post helped.

Answer 2

Hi Ryan,

According to your description, did you try to turn on TLS 1.0, TLS1.1, AND TLS1.2 in Advanced settings based on the warning message? What’s the browser did you use when the warning message occur? Are the browser same between the computers you tested?

As Vished posted, configure SSL connections on a native mode Report Server, we need to bind SSL to a Reporting Service URL reservation. And the certificate you installed should be a server certificate(client certificates are not supported). And if you are running IIS and Reporting Services together on the same computer, please pay attention to the interoperability with IIS. For more information, please refer to following link:

Configure SSL Connections on a Native Mode Report Server

If you still have any questions, please feel free to ask.

Best Regards,
Pirlo Zhang

---

MSDN Community Support<br/> Please remember to click &quot;Mark as Answer&quot; the responses that resolved your issue, and to click &quot;Unmark as Answer&quot; if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact <a href="mailto:[e-mail]">[e-mail]</a>.

Answer 3

Pirlo,

Thank you for responding.  I saw this article and the SSL cert is successfully bound and installed in SSRS.  Which is why it is very strange that it doesn't work locally, but I can copy the same link and successfully connect from my computer.

Thanks, Ryan

Answer 4

Vishe,

The SSL Certs are successfully bound, I did see this article as well.  I don't know if this is caused, because the SSL cert I am testing with is just a standard Cert for one name which is the FQDN of my server and not an UCC cert.  I would assume that if it wasn't bound properly then I wouldn't be able to connect via my computer either, but if I use the same URL on computer it works.  I have even changed the cert to a godaddy cert that I can use for testing and I am encountering the same issue.

Thanks, Ryan

Answer 5

Hi Ryan,

Did you edit entries for UrlResevations, to set the desired url’s for SSL in RsReportServer.config file usually located in C:\Program Files\Microsoft SQL Server\MSRS13.MSSQLSERVER\Reporting Services\ReportServer?

Reference: Configure SSRS for SSL

And you can enable verbose logging in Reporting Services to get more detailed information about this issue.

Reference: Recommended configuration for Verbose Logging in Reporting Services

Best Regards,
Pirlo Zhang

---

MSDN Community Support
Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact [e-mail].

Answer 6

I am not sure what caused this issue, but I found out that I had to have SQL Standard or better for MBAM so I had to essentially start over.  After I installed SQL 2014 Standard and install the SSL Cert I didn't have the same issue.  I could access the Report URLs locally or remotely as I expected via SSL with no issues.  I had to push a policy and add our external Domain and internal domain to the Local Internet Security zone for IE as well.

Thanks for the posts and Support.

Ryan