Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
SSL related issue when running on Linux + Electron
See original GitHub issueActual Results
I see this in the main process when running Studio 2.2.0:
/tmp/.mount_instal7w6CmU/app/realm-stu: symbol lookup error: /tmp/.org.chromium.Chromium.t4Fezq: undefined symbol: SSL_get0_param
Steps to Reproduce
- Start an Ubuntu 16.04 box
- Download Studio 2.2.0 from https://studio-releases.realm.io/v2.2.0/download/linux-appimage
- Change permissions to allow the AppImage to be executed
- Execute Studio it from a terminal
- Connect to a server Realm to observe the error in the terminal from which Studio was launched
Code Sample
N/A
Version of Realm and Tooling
- Realm JS SDK Version: 2.6.0
- Node or React Native: Electron
- Client OS & Version: Ubuntu 16.04
- Which debugger for React Native: N/A
Issue Analytics
- State:
- Created 5 years ago
- Comments:9 (6 by maintainers)
Top Results From Across the Web
https://service.electron.build uses invalid SSL certificate ...
When app-builder tries to access https://service.electron.build/find-build-agent , it results in an error because of the invalid SSL certificate ...
Read more >Issues with Electron and expired root - Help
Our Electron (https://www.electronjs.org/) application is failing to connect to websites using LE certificates.
Read more >How do I trust a self signed certificate from an electron app?
How can I trust that certificate from my electron app? Right now I get: Failed to load resource: net::ERR_INSECURE_RESPONSE. ssl · https ...
Read more >Install SSL Certificate for Electron Application - Ask Ubuntu
I'm currently building a debian installation package to deploy a electron application to our internal linux desktop machines (Ubuntu 16.04).
Read more >9 Methods to Fix NET::ERR_CERT_COMMON_NAME_INVALID
1. Verify That Your SSL Certificate Is Correct · Verifying Wildcard SSL Certificates · Verifying Subject Alternative Names (SAN) Certificates.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve investigated the issue and it turns out that OpenSSL is correctly linked statically, but it’s an older version. Because we build realm-js on CentOS 6.1 (in order to support old enough Glibc versions) we also link against that distribution’s OpenSSL which is 1.0.1, while the realm-sync static library uses APIs introduced in OpenSSL 1.0.2, hence the missing symbol errors. I’ll try to get the Dockerfile to build OpenSSL 1.0.2k so we can link against that, but it was really unfortunate that realm-sync upgraded to an OpenSSL version not available on one of our supported systems.
It doesnt work with OpenSSL 1.0.1. It compiles, but when you run the electron app, it will cause undefined symbol: SSL_library_init error. Thanks to fealebenpae for finding the cause of this problem.