This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
Hi,
I have added a certificate (not self signed) and enabled SSL on our development server. The first hurdle was that the alternate machine names were not recognised by the power bi server (!!). This article fixed that: https://support.microsoft.com/en-sg/help/2418246/you-cannot-view-some-of-your-ssl-certificates-in-re...
However when I disabled the port 80 bindings, I could no longer upload reports from the desktop, despite referencing the server on :443. The 3-dots menu on each report no longer works either.
It seems you *must* have port 80 enabled to use report server.
Can anyone confirm this is true and/or offer a way for us to work solely over SSL?
have you found a solution?
Hy @mketechguy what we ended up doing is restricting access to port 80 on the firewall of the on prem. report server. this way system internal communication with port 80 seems still to work (which afaik is needed by report server to work). its been running like that for a couple of days and so far we didnt have any issues. if anyone else has a better solution feel free to share it.
regards, Thomas
Did you ever find a solution to this?
Check out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 2 | |
| 1 | |
| 1 | |
| 1 | |
| 1 |