Forum Discussion

Battar's avatar
Battar
Frequent Visitor
1 year ago
Solved

The MySql source doesn't support encrypted connections when i try to trying to automate the refresh

Hallo all, 

 

I’m currently trying to automate the refresh of a dashboard connected to a MySQL database using Power BI Service (Online).

 

Although I have disabled encryption both in Power BI Desktop and in the Power BI Service data source settings, I still receive an error related to encrypted connections when trying to schedule or trigger a refresh online.

 

I've checked the following:

 

The connection works perfectly in Power BI Desktop.

 

Encryption is explicitly disabled in both environments.

 

The data gateway is correctly installed and running.

 

However, Power BI Service continues to reject the connection, assuming encryption is required.

 

I’ve tried many solutions but nothing worked so far.

Do you have any recommendations or workaround to solve this encryption conflict?

the issue msg "The MySql source doesn't support encrypted connections. (Source at X.XX.XXX.X:3306;xxx.). The exception was raised by the IDbCommand interface. Table:xxxx."

 

Thanks in advance,

  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi Battar,

    Thanks for reaching out to the Microsoft fabric community forum. It looks like you are facing an error related to encrypted connections when trying you are to schedule or trigger a refresh online. As you have already went through couple of solutions and workarounds, kindly go through few more workarounds to narrow down the issue. Some recent MySQL connector versions have caused provider errors with the gateway, so connector version mismatch is a frequent cause of this exact error. Enabling SSL on the server is an alternative fix because the service sometimes attempts an encrypted connection by default.

    As you have akready checked the gateway machine, once verify if you can connect to X.XX.XXX.X:3306 (telnet / PowerShell / MySQL client). If the gateway is in a different environment (VM, Azure VM, etc.), ensure outbound/inbound rules allow the traffic and the MySQL user is allowed from the gateway host.

     

     

    If none of the above help, at this point it may be worth opening a support ticket with Microsoft. You can reach out to Microsoft Support by raising a ticket with Microsoft Support. Please refer below link on how to raise a contact support or support ticket.
    How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

     

     

    If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

    Best Regards,
    Hammad.

  • Anonymous's avatar
    Anonymous
    1 year ago

    Hi Battar,

    Power BI Service will only use your MySQL gateway data source if the dataset is mapped to the gateway entry that exactly matches the server name/port used in Desktop, and the gateway host must have a compatible MySQL connector installed. The "SslMode=none;" override is the usual fix when the gateway is trying to open an encrypted connection but your MySQL server doesn’t accept SSL. Kindly follow these steps in order and test after each one.

    * Edit the gateway data source and add the connection string override. In PBI Service go to Settings (gear) then Manage gateways and select choose your gateway and click the MySQL data source you created. In the data source edit screen look for the Connection string override (sometimes under Advanced settings). Add "SslMode=none;".

    * Now on the gateway machine restart the “On-premises data gateway” Windows service (or reboot the gateway VM). This makes sure the new connector/override is picked up.

    * Makew sure the gateway has the MySQL client/connector. If you already have a connector installed, try a different version (some connector versions have caused issues with the gateway).

    * Confirm dataset (gateway mapping and credentials). In Power BI Service go to your Workspace then go to Datasets and then the dataset and then Settings and then Gateway connection. Make sure the dataset is mapped to the same gateway data source entry you edited.

    Now test connectivity from the gateway host and if you made changes while the dataset already existed in the service, republish the PBIX.

     

    If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

    Best Regards,
    Hammad.

7 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Battar,

    Thanks for reaching out to the Microsoft fabric community forum. It looks like you are facing an error related to encrypted connections when trying you are to schedule or trigger a refresh online. As you have already went through couple of solutions and workarounds, kindly go through few more workarounds to narrow down the issue. Some recent MySQL connector versions have caused provider errors with the gateway, so connector version mismatch is a frequent cause of this exact error. Enabling SSL on the server is an alternative fix because the service sometimes attempts an encrypted connection by default.

    As you have akready checked the gateway machine, once verify if you can connect to X.XX.XXX.X:3306 (telnet / PowerShell / MySQL client). If the gateway is in a different environment (VM, Azure VM, etc.), ensure outbound/inbound rules allow the traffic and the MySQL user is allowed from the gateway host.

     

     

    If none of the above help, at this point it may be worth opening a support ticket with Microsoft. You can reach out to Microsoft Support by raising a ticket with Microsoft Support. Please refer below link on how to raise a contact support or support ticket.
    How to create a Fabric and Power BI Support ticket - Power BI | Microsoft Learn

     

     

    If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

    Best Regards,
    Hammad.

  •  

    In Power BI Service under Manage gateways go to your gateway and edit the data source add a connection string override with :

    SslMode=none;

     

    Solved: Re: Power BI Gateway MySQL source doesn't support ... - Microsoft Fabric Community

    Solved: Data Refresh Failed: mysql doesn't support encrypt... - Microsoft Fabric Community

     

    If your security policy allows, it’s cleaner to enable SSL/TLS on the MySQL server and use encrypted connections end-to-end. (You can ask the admin to do that) :

    https://learn.microsoft.com/en-us/azure/mysql/flexible-server/how-to-connect-tls-ssl

     

    • Battar's avatar
      Battar
      Frequent Visitor

      I stell have the problem, here some Screanshot maby helping u to understand me

        

      • Anonymous's avatar
        Anonymous
        Not applicable

        Hi Battar,

        Power BI Service will only use your MySQL gateway data source if the dataset is mapped to the gateway entry that exactly matches the server name/port used in Desktop, and the gateway host must have a compatible MySQL connector installed. The "SslMode=none;" override is the usual fix when the gateway is trying to open an encrypted connection but your MySQL server doesn’t accept SSL. Kindly follow these steps in order and test after each one.

        * Edit the gateway data source and add the connection string override. In PBI Service go to Settings (gear) then Manage gateways and select choose your gateway and click the MySQL data source you created. In the data source edit screen look for the Connection string override (sometimes under Advanced settings). Add "SslMode=none;".

        * Now on the gateway machine restart the “On-premises data gateway” Windows service (or reboot the gateway VM). This makes sure the new connector/override is picked up.

        * Makew sure the gateway has the MySQL client/connector. If you already have a connector installed, try a different version (some connector versions have caused issues with the gateway).

        * Confirm dataset (gateway mapping and credentials). In Power BI Service go to your Workspace then go to Datasets and then the dataset and then Settings and then Gateway connection. Make sure the dataset is mapped to the same gateway data source entry you edited.

        Now test connectivity from the gateway host and if you made changes while the dataset already existed in the service, republish the PBIX.

         

        If I misunderstand your needs or you still have problems on it, please feel free to let us know.  

        Best Regards,
        Hammad.