google-cloud-print-connector - SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
Clash Royale CLAN TAG#URR8PPP
I have an ancient CentOS 5.11 installation on an inhouse server. The server is due for upgrade in a few months but till then, I'm stuck with 5.11.
I intend to install google-cloud-print-connector but it isn't available in any repo so I'm trying to source compile it.
I have already installed all prerequisites, some from alternate repos, others source compiled however when trying to run
go get github.com/google/cloud-print-connector/...
I get the following error
# cd .; git clone https://github.com/google/cloud-print-connector /home/go/src/github.com/google/cloud-print-connector
Cloning into '/home/go/src/github.com/google/cloud-print-connector'...
fatal: unable to access 'https://github.com/google/cloud-print-connector/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
package github.com/google/cloud-print-connector/...: exit status 128
There are many questions here regarding this error however none of the suggested solutions work.
I have git version 2.9.5, openssl-1.0.2a, curl-7.42.1 which all support TLS v1.2.
I also tried git config --global --add http.sslVersion tlsv1.2 and other tls variants but to no avail.
Any ideas?
linux git ssl
edited Jan 11 at 15:26
Jeff Schaller
40.1k1054126
add a comment |
I have an ancient CentOS 5.11 installation on an inhouse server. The server is due for upgrade in a few months but till then, I'm stuck with 5.11.
I intend to install google-cloud-print-connector but it isn't available in any repo so I'm trying to source compile it.
I have already installed all prerequisites, some from alternate repos, others source compiled however when trying to run
go get github.com/google/cloud-print-connector/...
I get the following error
# cd .; git clone https://github.com/google/cloud-print-connector /home/go/src/github.com/google/cloud-print-connector
Cloning into '/home/go/src/github.com/google/cloud-print-connector'...
fatal: unable to access 'https://github.com/google/cloud-print-connector/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
package github.com/google/cloud-print-connector/...: exit status 128
There are many questions here regarding this error however none of the suggested solutions work.
I have git version 2.9.5, openssl-1.0.2a, curl-7.42.1 which all support TLS v1.2.
I also tried git config --global --add http.sslVersion tlsv1.2 and other tls variants but to no avail.
Any ideas?
linux git ssl
edited Jan 11 at 15:26
Jeff Schaller
40.1k1054126
If the machine is telling you it is you are using non supported protocols, why not fixing the situation instead of not believing and trying to fix it?
– Rui F Ribeiro
Jan 11 at 8:49
Care to elaborate? The error says I need to use TLS 1.0 and I tried that along with other TLS as well.
– user330934
Jan 11 at 9:06
1407742E "tlsv1 alert protocol version" does not mean you "need to use TLS1.0"; it means the alert code for protocol version (70) was first defined in TLS1.0. github since about a year ago only supports TLS1.2 and apparently you're not sending it but I have no clue why. As a start tryopenssl s_client -connect github.com:443 -debugand see whether that succeeds (with 1.2) (note: many hosts nowadays require-servernameons_clientfor SNI but github currently doesn't)
– dave_thompson_085
Jan 11 at 11:31
As far as I know, github only supports TLS1.2 and newer; RHEL 5 only supports TLS1.1 and older. So thegitcommand that comes with CentOS5 won't talk to github any more.
– Stephen Harris
Jan 11 at 15:51
add a comment |
I have an ancient CentOS 5.11 installation on an inhouse server. The server is due for upgrade in a few months but till then, I'm stuck with 5.11.
I intend to install google-cloud-print-connector but it isn't available in any repo so I'm trying to source compile it.
I have already installed all prerequisites, some from alternate repos, others source compiled however when trying to run
go get github.com/google/cloud-print-connector/...
I get the following error
# cd .; git clone https://github.com/google/cloud-print-connector /home/go/src/github.com/google/cloud-print-connector
Cloning into '/home/go/src/github.com/google/cloud-print-connector'...
fatal: unable to access 'https://github.com/google/cloud-print-connector/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
package github.com/google/cloud-print-connector/...: exit status 128
There are many questions here regarding this error however none of the suggested solutions work.
I have git version 2.9.5, openssl-1.0.2a, curl-7.42.1 which all support TLS v1.2.
I also tried git config --global --add http.sslVersion tlsv1.2 and other tls variants but to no avail.
Any ideas?
linux git ssl
edited Jan 11 at 15:26
Jeff Schaller
40.1k1054126
I have an ancient CentOS 5.11 installation on an inhouse server. The server is due for upgrade in a few months but till then, I'm stuck with 5.11.
I intend to install google-cloud-print-connector but it isn't available in any repo so I'm trying to source compile it.
I have already installed all prerequisites, some from alternate repos, others source compiled however when trying to run
go get github.com/google/cloud-print-connector/...
I get the following error
# cd .; git clone https://github.com/google/cloud-print-connector /home/go/src/github.com/google/cloud-print-connector
Cloning into '/home/go/src/github.com/google/cloud-print-connector'...
fatal: unable to access 'https://github.com/google/cloud-print-connector/': error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
package github.com/google/cloud-print-connector/...: exit status 128
There are many questions here regarding this error however none of the suggested solutions work.
I have git version 2.9.5, openssl-1.0.2a, curl-7.42.1 which all support TLS v1.2.
I also tried git config --global --add http.sslVersion tlsv1.2 and other tls variants but to no avail.
Any ideas?
linux git ssl
linux git ssl
edited Jan 11 at 15:26
Jeff Schaller
40.1k1054126
edited Jan 11 at 15:26
Jeff Schaller
40.1k1054126
edited Jan 11 at 15:26
Jeff Schaller
40.1k1054126
edited Jan 11 at 15:26
Jeff Schaller
40.1k1054126
edited Jan 11 at 15:26
Jeff Schaller
40.1k1054126
40.1k1054126
asked Jan 11 at 7:46
user330934
If the machine is telling you it is you are using non supported protocols, why not fixing the situation instead of not believing and trying to fix it?
– Rui F Ribeiro
Jan 11 at 8:49
Care to elaborate? The error says I need to use TLS 1.0 and I tried that along with other TLS as well.
– user330934
Jan 11 at 9:06
1407742E "tlsv1 alert protocol version" does not mean you "need to use TLS1.0"; it means the alert code for protocol version (70) was first defined in TLS1.0. github since about a year ago only supports TLS1.2 and apparently you're not sending it but I have no clue why. As a start tryopenssl s_client -connect github.com:443 -debugand see whether that succeeds (with 1.2) (note: many hosts nowadays require-servernameons_clientfor SNI but github currently doesn't)
– dave_thompson_085
Jan 11 at 11:31
As far as I know, github only supports TLS1.2 and newer; RHEL 5 only supports TLS1.1 and older. So thegitcommand that comes with CentOS5 won't talk to github any more.
– Stephen Harris
Jan 11 at 15:51
add a comment |
If the machine is telling you it is you are using non supported protocols, why not fixing the situation instead of not believing and trying to fix it?
– Rui F Ribeiro
Jan 11 at 8:49
Care to elaborate? The error says I need to use TLS 1.0 and I tried that along with other TLS as well.
– user330934
Jan 11 at 9:06
1407742E "tlsv1 alert protocol version" does not mean you "need to use TLS1.0"; it means the alert code for protocol version (70) was first defined in TLS1.0. github since about a year ago only supports TLS1.2 and apparently you're not sending it but I have no clue why. As a start tryopenssl s_client -connect github.com:443 -debugand see whether that succeeds (with 1.2) (note: many hosts nowadays require-servernameons_clientfor SNI but github currently doesn't)
– dave_thompson_085
Jan 11 at 11:31
As far as I know, github only supports TLS1.2 and newer; RHEL 5 only supports TLS1.1 and older. So thegitcommand that comes with CentOS5 won't talk to github any more.
– Stephen Harris
Jan 11 at 15:51
If the machine is telling you it is you are using non supported protocols, why not fixing the situation instead of not believing and trying to fix it?
– Rui F Ribeiro
Jan 11 at 8:49
If the machine is telling you it is you are using non supported protocols, why not fixing the situation instead of not believing and trying to fix it?
– Rui F Ribeiro
Jan 11 at 8:49
Care to elaborate? The error says I need to use TLS 1.0 and I tried that along with other TLS as well.
– user330934
Jan 11 at 9:06
Care to elaborate? The error says I need to use TLS 1.0 and I tried that along with other TLS as well.
– user330934
Jan 11 at 9:06
1407742E "tlsv1 alert protocol version" does not mean you "need to use TLS1.0"; it means the alert code for protocol version (70) was first defined in TLS1.0. github since about a year ago only supports TLS1.2 and apparently you're not sending it but I have no clue why. As a start try
openssl s_client -connect github.com:443 -debug and see whether that succeeds (with 1.2) (note: many hosts nowadays require -servername on s_client for SNI but github currently doesn't)– dave_thompson_085
Jan 11 at 11:31
1407742E "tlsv1 alert protocol version" does not mean you "need to use TLS1.0"; it means the alert code for protocol version (70) was first defined in TLS1.0. github since about a year ago only supports TLS1.2 and apparently you're not sending it but I have no clue why. As a start try
openssl s_client -connect github.com:443 -debug and see whether that succeeds (with 1.2) (note: many hosts nowadays require -servername on s_client for SNI but github currently doesn't)– dave_thompson_085
Jan 11 at 11:31
As far as I know, github only supports TLS1.2 and newer; RHEL 5 only supports TLS1.1 and older. So the
git command that comes with CentOS5 won't talk to github any more.– Stephen Harris
Jan 11 at 15:51
As far as I know, github only supports TLS1.2 and newer; RHEL 5 only supports TLS1.1 and older. So the
git command that comes with CentOS5 won't talk to github any more.– Stephen Harris
Jan 11 at 15:51
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "106"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: false,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: null,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493885%2fgoogle-cloud-print-connector-ssl23-get-server-hellotlsv1-alert-protocol-versi%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Unix & Linux Stack Exchange!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f493885%2fgoogle-cloud-print-connector-ssl23-get-server-hellotlsv1-alert-protocol-versi%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
If the machine is telling you it is you are using non supported protocols, why not fixing the situation instead of not believing and trying to fix it?
– Rui F Ribeiro
Jan 11 at 8:49
Care to elaborate? The error says I need to use TLS 1.0 and I tried that along with other TLS as well.
– user330934
Jan 11 at 9:06
1407742E "tlsv1 alert protocol version" does not mean you "need to use TLS1.0"; it means the alert code for protocol version (70) was first defined in TLS1.0. github since about a year ago only supports TLS1.2 and apparently you're not sending it but I have no clue why. As a start try
openssl s_client -connect github.com:443 -debugand see whether that succeeds (with 1.2) (note: many hosts nowadays require-servernameons_clientfor SNI but github currently doesn't)– dave_thompson_085
Jan 11 at 11:31
As far as I know, github only supports TLS1.2 and newer; RHEL 5 only supports TLS1.1 and older. So the
gitcommand that comes with CentOS5 won't talk to github any more.– Stephen Harris
Jan 11 at 15:51