Connections To MySQL Fail Using The mysql2 Package

[jabarihunt]

What version of Bun is running?

• 1.0.2+37edd5a6e389265738e89265bcbdf2999cb81a49
• 1.0.3+25e69c71e70ac8a0a88f9cf15b4057bd7b2a633a

What platform is your computer?

Darwin 22.6.0 arm64 arm

What steps can reproduce the bug?

const mysql = require('mysql2');

const getMySQLPool = (credentials) => {

    // SET INITIAL CONFIGURATION PARAMETERS

        let config = {
            user: credentials.username,
            password: credentials.password,
            database: credentials.database,
            connectionLimit: 1,
            waitForConnections: true,
            charset : 'utf8mb4'
        };

    // SET PARAMETERS FOR A SOCKET OR TCP CONNECTION

        if (credentials.socket) {
            config.socketPath = credentials.socket;
        } else {
            config.host = credentials.host;
            config.port = credentials.port;
        }

    // RETURN CONNECTION POOL

        return mysql.createPool(config);

};

const db = getMySQLPool({
    host: "xx.xxx.xxx.xxx",
    port: 3306,
    database: "database_name",
    username: "user",
    password: "xxxxxxxxxxx"
});

const queryDb = async (db, query) => {
    return new Promise(async (resolve) => {
        db.query(query.trim(), (error, results) => {

            if (error) {
                console.error(`DATABASE QUERY ERROR: ${error} | QUERY: ${query}`);
                resolve(null);
                 return;
            }

            resolve(results);

        });
    });
};

const results = await queryDb(db, "SELECT id FROM some_table LIMIT 1");

What is the expected behavior?

1. A successful connection to the database is made via a connection pool.
2. The query is executed and a result returned.

What do you see instead?

• When connecting to my localhost, the connection times out.
• When connecting to a MySQL instance hosted on GCP Cloud SQL, I receiving the following error: Error: Access denied for user 'user'@'xx.xxx.xx.xxx' (using password: YES)

I have double checked the credentials for both instances. I can connect with my credentials using local GUI tools as well (Beekeper, TablePlus, etc).

Additional information

• mysql2 version 3.6.1
• I forgot to mention, this is within an Express app.
• UPDATE: Also happeing in Bun 1.0.3

[jabarihunt]

Began working with Bun ~1.5~ 1.0.5.

[balazshevesi]

bro is living in the future. we're on bun v1.0.22, he's already on v.1.5.

nah but fr, im on the latest verison of bun and mysql2 and im getting the same error. it's strange asf, im migrating a nextjs api to bun (with hono and drizzle orm). mysql2 connects fine when running in nextjs, but not on my dedicated bun backend. i've checked the environment variables, and there's nothing wrong there.

could it be something with the database server (im hosting it on aws rds)? are there any weird sneaky headers that are being included that rds doesn't like or what?

[jabarihunt]

@Balazs-topg bro is living in the future. we're on bun v1.0.22, he's already on v.1.5.

😆 Corrected! Not sure why it's not working for you, maybe it was fixed then broken again in a later update.

[andreigoea]

I'm getting the same issue on latest version whilst trying to use mysql2 in a SvelteKit application. Works fine if I just run it with Node.

[balazshevesi]

i fixed it by moving my database from AWS RDS to railway.app, im still not sure what the actual root cause was though

[abdoufma]

I ran into this problem recently, not only using mysql2 package, but using mysql as well. With mysql2, the connection times out. With mysql it hangs indefinitely when establishing the connection.

[MarcoHidalgo]

having the same issue right here. But at the same time not. Im using bun v1.1.13 and mysql2 to make an api with hono dev. The thing here is its works when i run the whole api, but if i try to run a single ts script, the console show this:

[abdoufma]

UPDATE : So, I was testing on ubuntu 22.04 / MySQL 8.0.37

But after testing on macOS 14.5 / MySQL 5.7.24 8.3.0, it worked fine:

EDIT : both systems running Bun v1.1.18 EDIT 2: it appears the MySQL server on my macOS system is actually 8.3.0 (for whatever reason mysql -V reported a different version string than SELECT @@version;)