Wrong SSL Version

[xell66]

1. Version 4.1.0
2. Ubuntu 16.04.1 LTS
3. CLI use
4. Did you encounter this recently, or has this bug always been there: -
5. Expected behaviour: get response
6. Comand: 'newman run collection.json --ssl-client-cert client.cer --ssl-client-key keyfile.key'

Hi there,
I have a Problem with Newman and I am not sure if its a Bug. First thing, this works on the same machine with the Postman application and the same URLs and certificates. I need to check if a connection is allowed with specific authetication certificates and want to automate this tests with newman. --insecure doesn't help and dont change the error. Has anyone an Idea? Thanks!

Comand in cli: 'newman run collection.json --ssl-client-cert client.cer --ssl-client-key keyfile.key'

LOGFILE:

→ Case1
GET https://XXXXX [errored]
tunneling socket could not be established, cause=write EPROTO 140000783112000:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:252:

→ Case2
GET https://XXXXX [errored]
tunneling socket could not be established, cause=write EPROTO 140000783112000:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:252:

→ Case3
GET https://XXXXXX [errored]
tunneling socket could not be established, cause=write EPROTO 140000783112000:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:252:

→ Case4
GET https://XXXXXX [errored]
tunneling socket could not be established, cause=write EPROTO 140000783112000:error:1408F10B:SSL routines:ssl3_get_record:wrong version number:../deps/openssl/openssl/ssl/record/ssl3_record.c:252:

[kunagpal]

@xell66

tunneling socket could not be established, cause=write EPROTO

This commonly occurs when you're using a proxy, but there's an attempt to send an HTTPS request via an HTTP proxy. Could you confirm that the HTTPS_PROXY environment variable is set correctly?

Similar to: #235

A detailed explanation can be found here:

1. https.get via proxy generates SSL3_GET_RECORD wrong version number error nodejs/node-v0.x-archive#6779
2. HTTP/HTTPS client requests throwing EPROTO nodejs/node#3692

[xell66]

Thanks for the advice. The Problem was that I used https_proxy and not HTTPS_PROXY.

[kunagpal]

@xell66 That's odd, the variable should work regardless of case 🤔

[shamasis]

Marking this as solved for now. Will revisit case issue during future chores.

[shamasis]

@mukeshsinghbhakuni590 - not sure how that relates to this issue. What am I missing?

[mukeshsinghbhakuni590]

@mukeshsinghbhakuni590 - not sure how that relates to this issue. What am I missing?

I m not relating it i m asking the solution to this issue.
Thanks.

[shamasis]

@mukeshsinghbhakuni590 Ok. The issue you’re posting seems to me like an npm issue and not anything related to Newman. Can you try running npm set strict-ssl false before npm install? If that doesn’t work, you should create a new issue on the correct project.