Closed metanovii closed 7 months ago
Try reverting to 3.9.2
. I was getting handshake errors today too (completely different setup than you, so no promises), and reverting from 3.9.3
back to 3.9.2
fixed it for me.
Try reverting to
3.9.2
. I was getting handshake errors today too (completely different setup than you, so no promises), and reverting from3.9.3
back to3.9.2
fixed it for me.
I rolled back the version to ^2.8.0 and it solved my problem. %)) And plugin auth mysql_native_password of course, sha2 does not work.
There's something weird with 3.9.3
. I was getting SSL cert errors on RDS with the newest version too. I upgraded the certs in the cluster and version 3.9.2
works fine with the newest certs provided by AWS, but 3.9.3
doesn't.
@pedrovanzella, can you show an example of your changes using the version 3.9.2?
@pedrovanzella, can you show an example of your changes using the version 3.9.2?
@wellwelwel there were no changes. I was running < 3.9.2
with the old RDS certs. I upgraded the cluster certs, and my code still worked. I upgraded to 3.9.3
, and I started getting errors related to the certificates (they were bubbled up to sequelize, as a SequelizeConnectionError: unable to get local issuer certificate
. I downgraded to 3.9.2
and I was able to connect again.
I mentioned this here in this issue because @BMO-tech had mentioned handshake errors, which is what this boiled down to - following the stack down I would see HANDSHAKE_SSL_ERROR
.
@pedrovanzella, @BMO-tech
I think the PR #2542 fixes this behavior, could you check it?
Closing this issue to continue this topic on #2541
@wellwelwel Just tested 3.9.4 and I still get the same behavior.
Thanks, @pedrovanzella 🙋🏻♂️
We are handing over this responsibility to a dependency dedicated to it: https://github.com/mysqljs/aws-ssl-profiles/issues/8
I'm thinking of "rebasing" the certificates again, just to make sure.
I trust this can be fixed soon.
@wellwelwel I commented on another issue already, but after some more testing, it does look like the issue is with RDS Proxy only. So it looks like you could just include the global CA certs in the file and we would be all set for all use cases.
version packages: percona mysql 8.0.34-26 nodejs version v18.13.0 mysql2 3.9.3
config
Debug log
messages from wireshark
What am I doing wrong?