"SSL connection error: unknown error number QMYSQL: Unable to connect"

[piervalli]

@DeadSo0ul
Copy the DLL in same folder of the excutable (debug and release)

[DeadSo0ul]

@SGaist
I think so.
Did I misunderstood?

I also tried what @piervalli suggested:
copying and pasting the .dll files to the folder that is my executable in
but without any success.

[piervalli]

@DeadSo0ul

What is version of Qt?
For 5.15.2 it uses openssl v1 instead for Qt6 openssl3

[DeadSo0ul]

@piervalli
QT Creator: 12.0.1
Qt: 6.6.0

I installed OpenSSL from their official site: https://www.openssl.org/source/.

I also tried the .dll files from the tools folder in the qt folder.

[piervalli]

@DeadSo0ul

You need understand if the library is loaded,
(This is usually test that I use for 5.15)

qDebug() << QSslSocket::supportsSsl() <<QSslSocket::sslLibraryBuildVersionString() << QSslSocket::sslLibraryVersionString()

[SGaist]

@DeadSo0ul said in "SSL connection error: unknown error number QMYSQL: Unable to connect":

@SGaist
I think so.
Did I misunderstood?

Yes, I wrote that you should add the path to the PATH environment variable. Not create a new one.

By the way, the Qt maintenance tool offers to download a pre-built version of OpenSSL, I would recommend using that one.

[DeadSo0ul]

@piervalli said in "SSL connection error: unknown error number QMYSQL: Unable to connect":

eed understand if the library is loaded,
(This is usually test that I use for 5.15)

I get a positive result for loading the library:

true "OpenSSL 3.0.7 1 Nov 2022" "OpenSSL 3.2.0 23 Nov 2023

[DeadSo0ul]

@SGaist
I understood this time and added

C:\Program Files\OpenSSL-Win64

as well as

C:\Qt\Tools\OpenSSLv3\Win_x64

to the Path variable.
That gave no result.

[piervalli]

@DeadSo0ul
Please check on Azure what is the minimum version of TLS supported. Some versions es 1.0 or 1.1 are declared by Microsoft deprecated.

https://learn.microsoft.com/en-us/azure/azure-resource-manager/management/tls-support

I think the mistage is tls version, in the documentation of driver
https://doc.qt.io/qt-6/sql-driver.html#qmysql
we have the flag MYSQL_OPT_TLS_VERSION
( I never tested is only an idea)

[DeadSo0ul]

@piervalli
The current tls version is 1.2 with an option to enable 1.3

How can I set that MYSQL_OPT_TLS_VERSION to 1.2 or possibly 1.3

[piervalli]

@DeadSo0ul

Try with

  db.setConnectOptions(QLatin1String("MYSQL_OPT_TLS_VERSION=TLSv1.2"))

Before db.open()

[DeadSo0ul]

Hi @piervalli
I tried adding db.setConnectOptions(QLatin1String("MYSQL_OPT_TLS_VERSION=TLSv1.2"));
I get these two errors:
QMYSQLDriver::open: Illegal connect option value 'MYSQL_OPT_TLS_VERSION=TLSv1.2'
and
QSqlError("2026", "QMYSQL: Unable to connect", "SSL connection error: unknown error number")

I will provide the whole .cpp file in case I am doing something wrong

#include "databasemanager.hpp"
#include <QSslSocket>
DatabaseManager::DatabaseManager() {

}

QSqlDatabase DatabaseManager::getDatabase() {
    return db;
}

void DatabaseManager::openConnection() {
    db = QSqlDatabase::addDatabase("QMYSQL");
    db.setHostName("name.mysql.database.azure.com");
    db.setPort(3306);  // Default MySQL port
    db.setDatabaseName("db");
    db.setUserName("admin");
    db.setPassword("admin");
    db.setConnectOptions(QLatin1String("MYSQL_OPT_TLS_VERSION=TLSv1.2"));

    if (db.open() && db.isOpen()) {
        qDebug() << "Database opened successfully";
    } else {
        // Handle connection error
        qDebug() << "Database failed to open";
        qDebug() << db.lastError();
        qDebug() << QSslSocket::supportsSsl() <<QSslSocket::sslLibraryBuildVersionString() << QSslSocket::sslLibraryVersionString();


    }
}

void DatabaseManager::closeConnection() {
    db.close();
}

[hskoglund]

Hi sometimes those setConnectionOptions() need a trailling semicolon, maybe try:

db.setConnectOptions("MYSQL_OPT_TLS_VERSION=TLSv1.2;");

[DeadSo0ul]

@hskoglund
I think I have done that in the provided code. Just before opening the database.

[DeadSo0ul]

Update:
The mistake was totally mine.
I was using Qt version 6.5.1. I updated to 6.6.1 and everything worked out.
Thanks everyone for helping!