prisma: sslaccept=accept_invalid_certs not working with mysql server 8.0.30

@Jolg42 Any intention on fixing this in an upcoming release?

I could reproduce on Google Cloud SQL with MySQL v8.0.30+ and locally with

version: "3.7"
services:
  mysql803:
    image: mysql:8.0.30
	# This does not change anything
    # command: --default-authentication-plugin=mysql_native_password
    restart: always
    environment:
      - MYSQL_ROOT_PASSWORD=root
      - MYSQL_DATABASE=tests
      - MYSQL_USER=prisma
    ports:
      - "3306:3306"

.env

DATABASE_URL="mysql://root:root@localhost:3306/16886?sslaccept=accept_invalid_certs"

With Prisma versions, 4.6.1, 4.7.1, 4.8.0. Example with prisma db push (it also errors with Prisma Client)

npx prisma db push
Environment variables loaded from prisma/.env
Prisma schema loaded from prisma/schema.prisma
Datasource "db": MySQL database "16886" at "34.89.164.209:3306"

Error: Migration engine error:
Bad handshake

Removing sslaccept=accept_invalid_certs makes this error disappear.

Release notes of MySQL 8.0.30 https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-30.html

Important Change: For platforms on which OpenSSL libraries are bundled, the linked OpenSSL library for MySQL Server has been updated to version 1.1.1o. Issues fixed in OpenSSL version 1.1.1o are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html. (Bug #34133985)

Release notes of MySQL 8.0.31 https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-31.html

Important Change: For platforms on which OpenSSL libraries are bundled, the linked OpenSSL library for MySQL Server has been updated to version 1.1.1q. Issues fixed in OpenSSL version 1.1.1q are described at https://www.openssl.org/news/cl111.txt and https://www.openssl.org/news/vulnerabilities.html. (Bug #34414695)

MySQL 8.0 error reference https://downloads.mysql.com/docs/mysql-errors-8.0-en.pdf

Error number: 1043; Symbol: ER_HANDSHAKE_ERROR; SQLSTATE: 08S01 Message: Bad handshake

Hi @Jolg42 May I ask if we have any plan to fix this bug?

@janpio thanks for following up, confirmed 4.11 fixes my issue

I can confirm that the prior reproduction from @Jolg42 does not fail any more with prisma@4.11.0-dev.51 (but did with prisma@4.10.1).

So this should now be fixed in our dev version which you can install via npm install prisma@dev @prisma/client@dev. Regenerate your Prisma Client and try again - and it should work. Would be very helpful if some of you could confirm this is indeed working now. Thanks!

+1

Same problem here with ?sslaccept=strict after creating a database on Azure and trying to connect, did exactly the same last week without trouble.

The connexion work with mysql cli

And I was able to restore data from the database, sounds more like a prisma issue no ?

Might be related: https://github.com/prisma/prisma/issues/15641 Same error, same MySQL version, and also trying to connect via SSL (with custom cert however).