-
Notifications
You must be signed in to change notification settings - Fork 449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to connect - error occurred during pre-login handshake. #1090
Comments
I can connect to the database via terminal. So it's not macOS that is causing the issue. |
Thanks for reporting this. The issue happens because of a bug with .Net Core 2.0 which is fixed in 2.1, so we'll need to publish an update with 2.1 soon. For more info see our discussion about the same issue in SQL Operations Studio. Unfortunately I don't have a workaround for you @jasperdunn, but you could try using SQL Operations Studio in the meantime since we've already fixed the bug there. |
@jasperdunn if you still need this functionality, try updating to 1.4.0 which we released yesterday. Some users have reported similar errors with .NET Core 2.1, which the new update uses, but it should fix it for most. Thanks! |
@MattIrv Fantastic! |
Now it works fine for me with 1.4.0 ! Thanks a lot ! 👍 |
Was there a solution to this, or just updating to the latest version? Because I am running latest versions of both, VS-Code as well as the extension and still have this error.
|
You can set TLS 1.0 to fix this. Also , this problem can be related to a firewall in the middle that is doing SSL inspection. I Suggest you either try again using another connection not doing SSL inspection, or ask your firewall admin to create an exemption for the source and/or destination you are connecting to, Cheers! |
I'm trying to connect to my database on AWS RDS. Since I've updated to 10.13.4 I haven't been able to connect to it.
Error message:
A connection was successfully established with the server, but then an error occurred during the pre-login handshake.
The text was updated successfully, but these errors were encountered: