Forum Discussion
Gateway stopped working - SSL certificate error
Hello cgapmmg,
If you still face the issue then please consider raising a support ticket for further assistance.This will allow the engineering team to investigate the issue in detail and provide a resolution or guidance.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft LearnThankyou for your understanding.
I solved it by adding the parameter AllowSelfSignedServerCert = 1 to the microsoft.impalaodbc.ini file, and that fixed the issue.
I was getting the error:
ODBC: ERROR [HY000] [Microsoft][DriverSupport] (1100) SSL certificate verification failed because the certificate is missing or incorrect
This happened after a server update, which now uses a self-signed certificate. I found that unless AllowSelfSignedServerCert is explicitly set to 1 in the microsoft.impalaodbc.ini file, the Microsoft Impala ODBC driver assumes a default value of 0, which causes the SSL certificate verification to fail.Now my gateway is running fine.
Thanks to everyone who tried to help!
Hi cgapmmg
Your on-premises data gateway is encountering an SSL certificate verification error when trying to connect to Impala from Power BI Service, despite working fine in Power BI Desktop. This issue is likely caused by incorrect SSL configurations in the Impala ODBC driver or permission-related problems with the gateway service. First, ensure that the microsoft.impalaodbc.ini file has the correct SSL Mode and the proper path to the trusted certificate. Also, verify that the gateway service is running under a user account with access to the database and certificates. Additionally, test the ODBC connection directly through the ODBC Data Source Administrator to check if the issue is specific to Power BI Service. If the problem persists, reinstall the latest gateway version, enable verbose logging, and review logs in C:\Users\<gateway_user>\AppData\Local\Microsoft\On-premises data gateway\. Also, check firewall settings to ensure that Impala’s SSL port is accessible and that the TLS version is compatible. Finally, update the Microsoft Impala ODBC driver, as some older versions have known SSL-related issues.
Thanks for your answer!
Here is what is written in my microsoft.impalaodbc.ini file:
[Driver]
AllowHostNameCNMismatch = 0
CheckCertRevocation = 0
Recently, my issue has changed. I'll explain it thoroughly below.
1. My Enterprise Gateway is installed and working.
2. Under "Manage Connections and Gateway", in the "On-premises data gateways" section, I can see my gateway Online, as shown below
3. However, when I try to schedule updates on my dashboard, it says that the Gateway or data sources are not reachable.
4. When I go to "Connections", and try to edit it to re-enter my credentials, i get the following error:
In english it says something like: "It is not possible to update the connection credentials. The data source could not be connected. The data source is inaccessible, a timeout error was reached, or the data source credentials are invalid. Check the data source configuration and contact a data source administrator to resolve this issue."
I'm sure my credentials are correct.
5. When I click "Update" at the dashboard, I get the following error:
It says that the SSL certificate verification failed, but I doubt this is the issue since I can't even see my gateway online when I try to schedule the updates.
I've updated the ODBC driver and tested it. It works perfectly. I even have a Personal Mode gateway connected directly to the ODBC, without the Impala connector, and it works fine.
Additionally, I have installed DBeaver on the computer where the gateway is running, and there I can access my database without any issues.
Thanks!
Hello cgapmmg,
If you still face the issue then please consider raising a support ticket for further assistance.This will allow the engineering team to investigate the issue in detail and provide a resolution or guidance.
To raise a support ticket for Fabric and Power BI, kindly follow the steps outlined in the following guide:
How to create a Fabric and Power BI Support ticket - Power BI | Microsoft LearnThankyou for your understanding.
Hi cgapmmg,
Could you please confirm if the issue has been resolved after raising a support case?
If a solution has been found, it would be greatly appreciated if you could share your insights with the community. This would be helpful for other members who may encounter similar issues.
Thank you for your understanding and assistance.
Hi v-sgandrathi !
My issue persists. I'm still working with the support to find a solution on it. The have my gateway log and browser log. I hope it will be solved soon.
Thanks!