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.
ssl3_get_record:wrong version number
See original GitHub issueConnectionError: write EPROTO 4392689088:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:332:
Your Environment
- node version: v13.2.0
@elastic/elasticsearchversion: v5.6.20- os: Mac
- any other relevant information
Issue Analytics
- State:
- Created 4 years ago
- Comments:5
Top Results From Across the Web
curl: (35) error:1408F10B:SSL routines:ssl3_get_record:wrong ...
The curl is not able to connect to server so it shows wrong version number. Set proxy by opening subl ~/.curlrc or use...
Read more >Unable to establish SSL connection: wrong version number
I have tried checking sslLabs and https://check-your-website.server-daten.de/?q=gencyberbook.com to find more details about the error, but not ...
Read more >Error:1408f10b:ssl routines:ssl3_get_record:wrong version ...
First, ensure the domain is pointing to the correct server. · Then, check the configuration file for our websites is enabled in Apache....
Read more >error:1408F10B:SSL routines:SSL3_GET_RECORD:wrong ...
I am configuring ssl for my kafka cluster. when I checked my configuration by this: openssl s_client -connect kafka-9092:9093 -tls1_2 ...
Read more >ERROR: 1408F10B:SSL routines:SSL3_GET_RECORD
This issue occurs when the services are running from more than one server which does not support the max version in one server....
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
try to request “http” instead of “https”. I solved the problem by it.
@LiangFuzhi did you figure this out? Currently experiencing the same.