azuredatastudio: Pre-login SSL/TLS handshake error
- SQL Operations Studio Version: 0.27.3
Steps to Reproduce:
- Have a SQL instance in AWS RDS running 11.00.6020.0.v1 using SSL provided by RDS (rds-ca-2015)
- Create connection from Mac 10.13.4 High Sierra to MS SQL instance
- User is a SQL login with default connection options.
- Click connect - receive error pop up with the following error
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 31 - Encryption(ssl/tls) handshake failed)
I have connected using this connection configuration before without issue. The only things I can remember changing between this working and not, are the upgrade to MacOS 10.13.4. Have also re-installed SQL Operations Studio, but this hasn’t resolved the issue.
Stacktrace gist - from Error box ‘Copy Details’
I noticed that dotnet/corefx has had a similar issue with the same error message raised in the last few days - https://github.com/dotnet/corefx/issues/28652 I wondered if it could be related?
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 1
- Comments: 21 (12 by maintainers)
I’m seeing the same problem. Any update on the resolution timeline?
I can confirm that this latest build does resolve the connection issue. I haven’t tested a ton of stuff yet, but basic queries work fine.
The April Public Preview build should contain the fix for this issue. So I’m close now. Please reactive the issue persists in the most recent build.
Thanks for confirming the test build resolves the issue. We’ll figure out the best way to include this fix in the next published build. Hopefully, if the final .Net Core 2.1 SDK update publishes tomorrow as planned we can just pick that up.
@sunildparte thanks for verifying. Unfortunately without a repro it’s a bit tricky to valid the fix. I’ll go back again and see why the preview .Net Core 2.1 bits aren’t getting included in the package, or if I have the wrong SDK version. I think the official .Net Core 2.1 SDK will be out on 4/17, but it would be great to validate that the SDK changes actually resolve this issue before then.
I’ll try to get an update test build out later tonight or tomorrow, once I figure out what’s going on. Thanks again!
@kburtram I still experience this problem with the above build 😕 Stacktrace gist - from Error box ‘Copy Details’