curl gnutls_handshake failed TLS connection was non-properly terminated
0
I would like to get the info from my custom Haystack service with the command
curl -v -X GET https://<myIP>:8443/api/haystack/about and it fails, the following is the log from above command
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying <myproxy-ip>...
* Connected to proxy.example.com (myproxy-ip) port 911 (#0)
* Establish HTTP proxy tunnel to <myIP>:8443
> CONNECT <myIP>:8443 HTTP/1.1
> Host: <myIP>:8443
> User-Agent: curl/7.47.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
<
* Proxy replied OK to CONNECT request
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 597 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* gnutls_handshake() failed: The TLS connection was non-properly terminated.
* Closing connection 0
curl: (35) gnutls_handshake() failed: The TLS connection was non-properly terminated.
At the same time, the Haystack service is having a front end web portal, when I access with Chrome, I can see the warning Privacy Error and NET::ERR_CERT_AUTHORITY_INVALID, but i still can proceed on the browser. I guess this might be the reason causing my curl fail.
Any idea?
Thanks
rest api curl
asked Nov 14 '18 at 2:51
Jeff Pang
145313
|
show 2 more comments
0
I would like to get the info from my custom Haystack service with the command
curl -v -X GET https://<myIP>:8443/api/haystack/about and it fails, the following is the log from above command
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying <myproxy-ip>...
* Connected to proxy.example.com (myproxy-ip) port 911 (#0)
* Establish HTTP proxy tunnel to <myIP>:8443
> CONNECT <myIP>:8443 HTTP/1.1
> Host: <myIP>:8443
> User-Agent: curl/7.47.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
<
* Proxy replied OK to CONNECT request
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 597 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* gnutls_handshake() failed: The TLS connection was non-properly terminated.
* Closing connection 0
curl: (35) gnutls_handshake() failed: The TLS connection was non-properly terminated.
At the same time, the Haystack service is having a front end web portal, when I access with Chrome, I can see the warning Privacy Error and NET::ERR_CERT_AUTHORITY_INVALID, but i still can proceed on the browser. I guess this might be the reason causing my curl fail.
Any idea?
Thanks
rest api curl
asked Nov 14 '18 at 2:51
Jeff Pang
145313
these kinds of errors are almost always caused by using old bugged versions of curl/tls libs, what doescurl --versionoutput?
– hanshenrik
Nov 14 '18 at 10:23
@hanshenrikcurl 7.47.0 (x86_64-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.4.10 zlib/1.2.8 libidn/1.32 librtmp/2.3
– Jeff Pang
Nov 14 '18 at 10:36
that's an early (january) 2016 version.. there's a good chance your problem would go away if you just updated curl & GnuTLS
– hanshenrik
Nov 14 '18 at 10:38
@hanshenrik updated curl to7.62.0and it gives another errorcurl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to <myIP>:<port>
– Jeff Pang
Nov 14 '18 at 11:25
what doescurl --versionsay now?
– hanshenrik
Nov 14 '18 at 12:31
|
show 2 more comments
0
0
0
I would like to get the info from my custom Haystack service with the command
curl -v -X GET https://<myIP>:8443/api/haystack/about and it fails, the following is the log from above command
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying <myproxy-ip>...
* Connected to proxy.example.com (myproxy-ip) port 911 (#0)
* Establish HTTP proxy tunnel to <myIP>:8443
> CONNECT <myIP>:8443 HTTP/1.1
> Host: <myIP>:8443
> User-Agent: curl/7.47.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
<
* Proxy replied OK to CONNECT request
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 597 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* gnutls_handshake() failed: The TLS connection was non-properly terminated.
* Closing connection 0
curl: (35) gnutls_handshake() failed: The TLS connection was non-properly terminated.
At the same time, the Haystack service is having a front end web portal, when I access with Chrome, I can see the warning Privacy Error and NET::ERR_CERT_AUTHORITY_INVALID, but i still can proceed on the browser. I guess this might be the reason causing my curl fail.
Any idea?
Thanks
rest api curl
asked Nov 14 '18 at 2:51
Jeff Pang
145313
I would like to get the info from my custom Haystack service with the command
curl -v -X GET https://<myIP>:8443/api/haystack/about and it fails, the following is the log from above command
Note: Unnecessary use of -X or --request, GET is already inferred.
* Trying <myproxy-ip>...
* Connected to proxy.example.com (myproxy-ip) port 911 (#0)
* Establish HTTP proxy tunnel to <myIP>:8443
> CONNECT <myIP>:8443 HTTP/1.1
> Host: <myIP>:8443
> User-Agent: curl/7.47.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
<
* Proxy replied OK to CONNECT request
* found 148 certificates in /etc/ssl/certs/ca-certificates.crt
* found 597 certificates in /etc/ssl/certs
* ALPN, offering http/1.1
* gnutls_handshake() failed: The TLS connection was non-properly terminated.
* Closing connection 0
curl: (35) gnutls_handshake() failed: The TLS connection was non-properly terminated.
At the same time, the Haystack service is having a front end web portal, when I access with Chrome, I can see the warning Privacy Error and NET::ERR_CERT_AUTHORITY_INVALID, but i still can proceed on the browser. I guess this might be the reason causing my curl fail.
Any idea?
Thanks
rest api curl
rest api curl
asked Nov 14 '18 at 2:51
Jeff Pang
145313
asked Nov 14 '18 at 2:51
Jeff Pang
145313
asked Nov 14 '18 at 2:51
Jeff Pang
145313
asked Nov 14 '18 at 2:51
Jeff Pang
145313
asked Nov 14 '18 at 2:51
Jeff Pang
145313
145313
these kinds of errors are almost always caused by using old bugged versions of curl/tls libs, what doescurl --versionoutput?
– hanshenrik
Nov 14 '18 at 10:23
@hanshenrikcurl 7.47.0 (x86_64-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.4.10 zlib/1.2.8 libidn/1.32 librtmp/2.3
– Jeff Pang
Nov 14 '18 at 10:36
that's an early (january) 2016 version.. there's a good chance your problem would go away if you just updated curl & GnuTLS
– hanshenrik
Nov 14 '18 at 10:38
@hanshenrik updated curl to7.62.0and it gives another errorcurl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to <myIP>:<port>
– Jeff Pang
Nov 14 '18 at 11:25
what doescurl --versionsay now?
– hanshenrik
Nov 14 '18 at 12:31
|
show 2 more comments
these kinds of errors are almost always caused by using old bugged versions of curl/tls libs, what doescurl --versionoutput?
– hanshenrik
Nov 14 '18 at 10:23
@hanshenrikcurl 7.47.0 (x86_64-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.4.10 zlib/1.2.8 libidn/1.32 librtmp/2.3
– Jeff Pang
Nov 14 '18 at 10:36
that's an early (january) 2016 version.. there's a good chance your problem would go away if you just updated curl & GnuTLS
– hanshenrik
Nov 14 '18 at 10:38
@hanshenrik updated curl to7.62.0and it gives another errorcurl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to <myIP>:<port>
– Jeff Pang
Nov 14 '18 at 11:25
what doescurl --versionsay now?
– hanshenrik
Nov 14 '18 at 12:31
these kinds of errors are almost always caused by using old bugged versions of curl/tls libs, what does
curl --version output?– hanshenrik
Nov 14 '18 at 10:23
these kinds of errors are almost always caused by using old bugged versions of curl/tls libs, what does
curl --version output?– hanshenrik
Nov 14 '18 at 10:23
@hanshenrik
curl 7.47.0 (x86_64-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.4.10 zlib/1.2.8 libidn/1.32 librtmp/2.3– Jeff Pang
Nov 14 '18 at 10:36
@hanshenrik
curl 7.47.0 (x86_64-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.4.10 zlib/1.2.8 libidn/1.32 librtmp/2.3– Jeff Pang
Nov 14 '18 at 10:36
that's an early (january) 2016 version.. there's a good chance your problem would go away if you just updated curl & GnuTLS
– hanshenrik
Nov 14 '18 at 10:38
that's an early (january) 2016 version.. there's a good chance your problem would go away if you just updated curl & GnuTLS
– hanshenrik
Nov 14 '18 at 10:38
@hanshenrik updated curl to
7.62.0 and it gives another error curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to <myIP>:<port>– Jeff Pang
Nov 14 '18 at 11:25
@hanshenrik updated curl to
7.62.0 and it gives another error curl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to <myIP>:<port>– Jeff Pang
Nov 14 '18 at 11:25
what does
curl --version say now?– hanshenrik
Nov 14 '18 at 12:31
what does
curl --version say now?– hanshenrik
Nov 14 '18 at 12:31
|
show 2 more comments
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
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
});
}
});
draft saved
draft discarded
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%2fstackoverflow.com%2fquestions%2f53292504%2fcurl-gnutls-handshake-failed-tls-connection-was-non-properly-terminated%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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.
draft saved
draft discarded
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%2fstackoverflow.com%2fquestions%2f53292504%2fcurl-gnutls-handshake-failed-tls-connection-was-non-properly-terminated%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
these kinds of errors are almost always caused by using old bugged versions of curl/tls libs, what does
curl --versionoutput?– hanshenrik
Nov 14 '18 at 10:23
@hanshenrik
curl 7.47.0 (x86_64-pc-linux-gnu) libcurl/7.47.0 GnuTLS/3.4.10 zlib/1.2.8 libidn/1.32 librtmp/2.3– Jeff Pang
Nov 14 '18 at 10:36
that's an early (january) 2016 version.. there's a good chance your problem would go away if you just updated curl & GnuTLS
– hanshenrik
Nov 14 '18 at 10:38
@hanshenrik updated curl to
7.62.0and it gives another errorcurl: (35) OpenSSL SSL_connect: SSL_ERROR_SYSCALL in connection to <myIP>:<port>– Jeff Pang
Nov 14 '18 at 11:25
what does
curl --versionsay now?– hanshenrik
Nov 14 '18 at 12:31