Skip to content
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

Closed
vincemaz opened this issue Jun 15, 2020 · 5 comments
Closed

SSL handshake failed: Premature end of input #2975

vincemaz opened this issue Jun 15, 2020 · 5 comments
Assignees

Comments

@vincemaz
Copy link

vincemaz commented Jun 15, 2020

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

$ node index.js
getApp() -> OK
User logged in: 5ee5f48261d4786a707d9af1
Connection[1]: Session[1]: client_reset_config = false, Realm exists = true, async open = false, client reset = false
Connection[1]: Connected to endpoint '75.2.1.110:443' (from '127.0.0.1:50066')
ERROR: Connection[1]: SSL handshake failed: Premature end of input
Connection[1]: Connection closed due to error

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

  • Realm JS SDK Version: v10.0.0-beta.6
  • Node: v12.18.0
  • Client OS & Version: Windows 10
@RealmBot
Copy link
Collaborator

➤ 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

realm.node!realm::SyncSession::revive_if_needed() Line 6 80 C++> realm.node!realm::SyncSession::revive_if_needed() Line 6 80 C+  realm.node!realm::SyncUser::registersession(std::sharedptrrealm::SyncSession session) Line 394 C  realm.node!realm::SyncManager::getsession(const std::string & path, const realm::SyncConfig & syncconfig, bool forceclientresync) Line 547 C  realm.node!realm::impl::RealmCoordinator::createsyncsession(bool forceclient_resync) Line 105 C  realm.node!realm::impl::RealmCoordinator::getsynchronized_realm(realm::Realm::Config config) Line 293 C  realm.node!realm::Realm::getsynchronizedrealm(realm::Realm::Config config) Line 155 C  realm.node!realm::js::RealmClassrealm::node::Types::asyncopenrealm(Napi::Env ctx, Napi::Object thisobject, realm::js::Argumentsrealm::node::Types & args, realm::js::ReturnValuerealm::node::Types & returnvalue) Line 874 C+

@kneth
Copy link
Contributor

kneth commented Jul 10, 2020

A fix was released in v10.0.0-beta.7

@sync-by-unito
Copy link

sync-by-unito bot commented Feb 24, 2023

➤ 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

@sync-by-unito
Copy link

sync-by-unito bot commented Feb 24, 2023

➤ 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.

@sync-by-unito
Copy link

sync-by-unito bot commented Feb 24, 2023

➤ On 2020-06-28, fealebenpae commented:

Realeased with realm-js 10.0.0-beta.7

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Mar 15, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants