-
Notifications
You must be signed in to change notification settings - Fork 585
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
SSL handshake failed: Premature end of input #2975
Comments
➤ Lyubomir Blagoev commented: This is an sync related issue Exception thrown at 0x0000000000000040 in node.exe: 0xC0000005: Access violation executing location 0x0000000000000040. here is the stack for it
|
A fix was released in v10.0.0-beta.7 |
➤ On 2020-06-17, blagoev commented: The fix for the access violation is found. This does not relate to the reported issue. Now we are able to reproduce the reported behavior and will continue to investigate |
➤ On 2020-06-23, fealebenpae commented: The SSL handshake error is because on Windows we use OpenSSL 1.0, and the Cloud load balancer requires a protocol and cipher suite combo that's newer than what OpenSSL 1.0 supports. The solution is to upgrade to OpenSSL 1.1, tracked in RSYNC-129. |
➤ On 2020-06-28, fealebenpae commented: Realeased with realm-js 10.0.0-beta.7 |
Goals
Trying to open to a synced realm with nodejs on Windows 10.
Note: The same code works fine on macOS.
Expected Results
Open synced realm without error.
Actual Results
Steps to Reproduce
Set up a simple nodejs project and run node index.js
Code Sample
https://gist.github.com/vincemaz/02f3a35adfa9d63897f02eb11378f8dc
Version of Realm and Tooling
The text was updated successfully, but these errors were encountered: