MySQL Connection Fails with [SSL: WRONG_VERSION_NUMBER] Despite Using ssl: false parameter

[claudio-ayma]

Hello MindsDB Team,

I am reporting a critical issue with the official mindsdb/mindsdb:latest Docker image. When attempting to connect to a standard MySQL server that does not use or require SSL, the MySQL handler ignores the officially documented "ssl": false parameter. It consistently attempts to initiate an SSL handshake, which then fails with an [SSL: WRONG_VERSION_NUMBER] error.

This behavior prevents connections to standard, non-SSL MySQL databases from the official MindsDB image.

Steps to Reproduce:

1. Use any standard MySQL server that is not configured to enforce SSL.

2. From an official mindsdb/mindsdb:latest Docker container, execute the following query, as specified in the documentation for disabling SSL:

   CREATE DATABASE mysql_connection_test
   WITH
     ENGINE = 'mysql',
     PARAMETERS = {
       "host": "192.168.30.16",
       "port": 3306,
       "user": "myuser",
       "password": "mypassword",
       "database": "mydatabase",
       "ssl": false
     };

Expected Behavior:

MindsDB should respect the "ssl": false parameter and establish a successful, non-encrypted connection to the MySQL database.

Actual Behavior:

The command fails with the following exception, indicating an SSL handshake was attempted:

mindsdb.api.executor.exceptions.ExecutorException: Can't connect to db: 2055: Lost connection to MySQL server at '192.168.30.16:3306', system error: Errno 1: [SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:1017)

Environment Details:

• MindsDB Version: latest (Tested on 2025-06-10)
• Installation Method: Official Docker Image (mindsdb/mindsdb:latest)
• MySQL Server Version: 5.7.22
• Host OS: Windows 10 + Docker

Exhaustive Troubleshooting Performed:

We have definitively isolated the issue to the MindsDB client-side handler.

1. Documented Method Fails: The primary issue is that "ssl": false does not work as expected.
2. Alternative Parameters Also Fail: We attempted other non-documented workarounds like "ssl_mode": "DISABLED" and "mysql_driver": "pymysql", all of which resulted in the same error.
3. Server Configuration Verified: We confirmed the MySQL server is not forcing the issue.
   • Global require_secure_transport is OFF.
   • The user account uses mysql_native_password and does not have a REQUIRE SSL clause.
4. Network Path Verified:
   • A different SQL client (DBeaver) on the same host machine connects successfully using a non-SSL connection.
   • A connection to an Oracle database from the same MindsDB container works perfectly, confirming Docker's network is functional.

Conclusion:

The official MindsDB Docker image appears to have a bug in its MySQL handler where it disregards the documented "ssl": false parameter, making it impossible to connect to non-SSL MySQL databases. This seems to be a client-side issue, not a server or network configuration problem.

Thank you for looking into this.