Forum Discussion
Power BI Report Server: HTTPS URL - Unable to find SSL Certificate
- 4 years ago
I'm not totally clear on what is going on with your server as you seem to be making contradictory statements. You show a screenshot where the certificate is not available, but then you say that you somehow bound it to port 8443... only one of these statements could be true.
To get HTTPS working you need to sort out the issue with the certificate drop down. If you have have not re-started the report server service try doing that as suggested in the documentation https://docs.microsoft.com/en-us/sql/reporting-services/security/configure-ssl-connections-on-a-native-mode-report-server?view=sql-server-ver15 If that does not work it could be a permissions issue so maybe try running the Report Server Configuration Manager as Admin and see if that helps.
niyati_61 wrote:
Since this 443 port doesn't seem to work, what all ports does Power BI Report Server work on?
Port 443 is the industry standard port for HTTPS connections, but if you cannot pick the certificate you will not be able to establish a HTTPS connection. So you need to get the certificate issue sorted out then HTTPS should start working on port 443
Hi niyati_61,
You can use any other port which is not reserved for Power BI Report Server, you can use Port [800 8020] depneding on your IT department guidelines.
d_gosbell, i have used / configured non-standards ports for configuring https on Power BI Report Server in many instances. The certificate needs to include / points to the correct Port number & after that it can be used.
If the https certificate is issued locally by your IT department, then it can be validated through your coorporate network. You can push this certificate to your Power BI Report Server machine. Once it's successfully published into it, you will be able to see it in your dropdown.
Regards,
Hasham
HashamNiaz wrote:
d_gosbell, i have used / configured non-standards ports for configuring https on Power BI Report Server in many instances. The certificate needs to include / points to the correct Port number & after that it can be used.
HashamNiaz yes, but that was not the question here. The OP was stating that 443 was not working. And I was saying that it should work once the certificate is correctly assigned. It is much simpler to use the standard port if you can as then you do not need to include the port number in the url
- HashamNiaz4 years ago
Solution Sage
Totally agreed d_gosbell