Forum Discussion
Issues connecting to MySQL database server using virtual network data gateway in Fabric
- Anonymous1 year ago
I managed to connect to connect to the external MySQL server using a Self-hosted Integration Runtime with a static IP address in Azure Data Factory. No luck in doing it in Fabric. I have not been able to raise a support ticket as I for some reason do not had access to do so.
Hi Anonymous ,
Thanks for reaching out to the Microsoft fabric community forum.
We really appreciate your detailed explanation. Since you verified that you can connect successfully from a VM in the same Virtual Network and Subnet, the issue is likely related to Fabric’s Virtual Network Data Gateway or Fabric’s ability to reach the database.
Here are the possible causes of the issue:
- Although the VM can access the MySQL database, the Virtual Network Data Gateway might be using a different subnet or IP range that is not whitelisted by the MySQL provider. The provider may need to whitelist additional Fabric-related IPs.
- The MySQL database provider may have firewall rules that allow only certain client types or sources. Fabric’s Virtual Network Gateway may use a different connection mechanism than a VM, which could be causing the block.
- Fabric might not support some MySQL authentication mechanisms that work on the VM. Verify if the database requires SSL/TLS, and ensure the correct SSL certificates are provided during the Fabric connection setup.
- Fabric’s Virtual Network Data Gateway does not use public IPs to connect but utilizes the configured Virtual Network. Any private endpoint restrictions could be blocking Fabric from connecting to MySQL.
- By default, MySQL uses port 3306, but some providers block external access to this port unless explicitly allowed. The provider may need to open this port.
I hope my suggestions give you good ideas, if you need any further assistance, feel free to reach out.
If this post helps, then please give us Kudos and consider Accept it as a solution to help the other members find it more quickly.
Thank you.
- Anonymous1 year agoNot applicable
Hello Anonymous ,
I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions. If my response has addressed your query, please accept it as a solution and give a 'Kudos' so other members can easily find it.
Thank you.- Anonymous1 year agoNot applicable
Hello Anonymous ,
I wanted to follow up on our previous suggestions regarding the issue. We would love to hear back from you to ensure we can assist you further.
If my response has addressed your query, please accept it as a solution and give a ‘Kudos’ so other members can easily find it. Please let us know if there’s anything else we can do to help.
Thank you.
- Anonymous1 year agoNot applicable
Hi!
Unfortunately, the connection issue still exists, and the advice given has not been able to resolve the issue. I have confirmed that port 3306 is open. When I troubleshoot the network in Fabric, I can see that the source adress indeed is an adress in my whitelisted subnet address range, and the remote adress is the adress of the MySQL database. However, the TCP test and ping still both fail.
What I feel most unsure about whether the issue exists on the Azure/Fabric side, or whether it is the server provider who has some security measure preventing my connection attempts.