Microsoft Fabric Community Conference 2025, March 31 - April 2, Las Vegas, Nevada. Use code FABINSIDER for a $400 discount.
Register nowThe Power BI DataViz World Championships are on! With four chances to enter, you could win a spot in the LIVE Grand Finale in Las Vegas. Show off your skills.
Hi
I am trying to fetch data to Power BI from a system that mainly uses client cert authentication with self-signed certificates. Since Power BI does not support client cert authentication, we are using api keys to the same endpoint. Despite disabling ssl verification from the server, I am still receiving the SSL trust relationship error with Power BI. However postman and other http clients can fetch the data from the same endpoint with api keys just fine, so the issue is with Power BI. There have been previous questions about the same thing here, and most seem to suggests two things:
1. Clear SSL state from internet options
2. Disable certificate revocation from Power BI options
I have done both of these things and still get the same error. The nginx server to which the requests are made simply logs a generic error: "client closed connection while waiting for request". Any ideas what might cause this?
Solved! Go to Solution.
In case anyone runs into this and has the exact same problem than I did, here is a solution I have not found elsewhere.
I raised a ticket from power platform admin center. We installed Fiddler Classic to collect trace logs. From Fiddler settings (tools -> options -> HTTPS) enabled "decrypt HTTPS traffic" and trusted the cert (not sure if this is a necessary step). With Fiddler running I tried to connect Power BI again, and got an error from Fiddler that said: "The server <ip> presented a certificate that did not validate, because it was issued to a different host". After clicking yes from the error dialog, power bi connected and the issue was fixed. Apparently Fiddler changed some windows wide setting to trust the cert, which power bi by itself couldn't handle (even though certificate revocation was turned off).
So if you are using self-signed certs and haven't paid attention to the common name of the cert, that might be the issue.
In case anyone runs into this and has the exact same problem than I did, here is a solution I have not found elsewhere.
I raised a ticket from power platform admin center. We installed Fiddler Classic to collect trace logs. From Fiddler settings (tools -> options -> HTTPS) enabled "decrypt HTTPS traffic" and trusted the cert (not sure if this is a necessary step). With Fiddler running I tried to connect Power BI again, and got an error from Fiddler that said: "The server <ip> presented a certificate that did not validate, because it was issued to a different host". After clicking yes from the error dialog, power bi connected and the issue was fixed. Apparently Fiddler changed some windows wide setting to trust the cert, which power bi by itself couldn't handle (even though certificate revocation was turned off).
So if you are using self-signed certs and haven't paid attention to the common name of the cert, that might be the issue.
yeah, this keeps cropping up.
You can raise an issue at https://community.fabric.microsoft.com/t5/Issues/idb-p/Issues . If you have a Pro license you can consider raising a Pro ticket at https://admin.powerplatform.microsoft.com/newsupportticket/powerbi
March 31 - April 2, 2025, in Las Vegas, Nevada. Use code MSCUST for a $150 discount!
Check out the February 2025 Power BI update to learn about new features.
User | Count |
---|---|
84 | |
78 | |
54 | |
39 | |
35 |
User | Count |
---|---|
99 | |
80 | |
49 | |
48 | |
48 |