How to fix the Azure MySql flexible server error "Failed to load MySQL flexible server databases" despite of many attempts.

Azure Sopago 20 Reputation points
2025-06-10T14:23:46.5866667+00:00

The Azure MySQL flexible server shows the error "Failed to load MySQL flexible server databases" in the azure portal. I also tried to access the server through MySQL workbench and it throws SSL connection error:error:0A00010B:ssl routines::wrong version number. The database was accessible very recently until this issue came up. The configuration of MySQL flexible server is Standard_B1ms (1 vCore, 2 GiB memory, 640 max iops). Please let me know of you have any insights on this. image-20250610-134120.png

Azure Database for MySQL
Azure Database for MySQL
An Azure managed MySQL database service for app development and deployment.
977 questions
0 comments No comments
{count} votes

Accepted answer
  1. Vijayalaxmi Kattimani 3,065 Reputation points Microsoft External Staff Moderator
    2025-06-10T17:13:44.13+00:00

    Hi Azure Sopago

    Greetings!

    As we understand that, you are running into the "Failed to load MySQL flexible server databases" error on the Azure portal, and you're also encountering an SSL connection error when trying to access the server with MySQL Workbench.

    Here are some steps you can take to troubleshoot and potentially resolve the issue:

    • Check SSL Configuration: Since you're getting a "wrong version number" SSL error, ensure that your MySQL Workbench is configured to use TLS 1.2. Azure Database for MySQL Flexible Server requires encrypted connections using TLS 1.2 and will reject connections using older TLS versions.
    • Firewall Settings: Make sure that the client IP address you are connecting from is allowed in the Azure Database for MySQL Flexible Server firewall settings. You can check this in the Azure portal under the Networking settings for your MySQL server.
    • Restart the MySQL Server: Sometimes simply restarting the MySQL server can resolve transient issues. This allows InnoDB’s crash recovery mechanism to kick in and potentially resolve any underlying faults.
    • Check Connection Parameters: Ensure that the connection string and credentials are correct when attempting to connect using MySQL Workbench. Any small typo can lead to connection issues.
    • Inspect the Server Logs: Check the server logs to see if there are any errors or warnings that could provide additional context. This would be in the "Diagnostic settings" or "Logs" settings under your MySQL server in the Azure portal.

    I hope, This response will address your query and helped you to overcome on your challenges.

    If this answers your query, do click Accept Answer and Yes for was this answer helpful. If you still have questions, please let us know what is needed in the comments so the question can be answered.

    Thank you for helping to improve Microsoft Q&A!

    1 person found this answer helpful.

0 additional answers

Sort by: Newest

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.