curl : (1) Protocol https not supported or disabled in libcurl

Question

I'm trying to install the Rails environments on Ubuntu 11.04. When I launch the command rvm install 1.9.2 --with-openssl-dir=/usr/local the following error is received:

curl : (1) Protocol https not supported or disabled in libcurl

How can this be resolved?

What happens if you don't use `--with-openssl-dir=/usr/local` (i.e. simply `rvm install 1.9.2`)? — Omri Barel, Jul 30 '11 at 17:45
I find it hard to believe that your curl doesn't support HTTPS. It's possible that rvm comes with its own curl, or that you didn't install curl (`sudo apt-get install curl`). Try `curl -o "google.html" https://google.com` to check if HTTPS is supported. — Omri Barel, Jul 30 '11 at 17:51

score 513 · Answer 1 · edited Aug 13 '16 at 10:09

513

Got the answer HERE for windows, it says there that:

curl -XPUT 'http://localhost:9200/api/twittervnext/tweet'

Woops, first try and already an error:

curl: (1) Protocol 'http not supported or disabled in libcurl

The reason for this error is kind of stupid, Windows doesn’t like it when you are using single quotes for commands. So the correct command is:

curl –XPUT "http://localhost:9200/api/twittervnext/tweet"

edited Aug 13 '16 at 10:09

melpomene

84,125
8
85
148

answered Jun 15 '14 at 17:53

cnlevy

10,630
3
20
21

2

use Windows SSL-enabled cURL http://curl.haxx.se/latest.cgi?curl=win64-ssl-sspi instead if none of the other provided answers works for windows. – ganesh Jan 08 '15 at 16:54
12

this is correct, and just to add a bit of salt, if you want to actually use the double quotes in the string you are quoting, then you need to escape them eg: `curl "http://localhost:3030/messages/" -H "Content-Type: application/json" --data-binary "{ \"name\":\"Curler\", \"text\": \"Hello from the command line\" }"` instead of `curl "http://localhost:3030/messages/" -H "Content-Type: application/json" --data-binary '{ "name":"Curler", "text": "Hello from the command line" }'`... take note of the single and unescaped double quotes on the wrong part. – Emmanuel Mahuni Dec 05 '17 at 20:54
1

@EmmanuelMahuni Thanks for the clue. I was running into the same issue while trying to CURL from bitbucket pipeline, my value includes double quotes (") (as i'm reading from json response from aws cli using jq), once after removing the double from start and end. it worked for me. Here is how i did it. `new_url=$( echo $url | tr -d \" )` – Appu Mistri May 25 '19 at 17:32
1

Having the same effect with curl on macOS. – not2savvy Jan 25 '20 at 19:29
1

Double quotes confirmed. =) – Ususipse Aug 10 '20 at 16:13
After nearly 20 years of using Linux, I am now forced to do something in Windows and - woops - stumbled over this, too. – rexkogitans Apr 09 '21 at 10:06
OMG. I was using curl on Windows but I wouldn't never expect this since I was running it trough Cygwin. – Bemipefe May 21 '21 at 15:13

score 113 · Answer 2 · edited Feb 21 '17 at 14:54

113

I ran into this problem and turned out that there was a space before the https which was causing the problem. " https://" vs "https://"

edited Feb 21 '17 at 14:54

Suhaib Janjua

3,538
16
59
73

answered Dec 15 '14 at 21:18

jbrahy

4,228
1
42
54

7

And I got same. I was surprised why the hell on the earth I am getting this error. :) +1 for sharing this. – Awais Qarni Dec 15 '15 at 13:25
3

Similar for me, it was a single quote because we had wrapped a default bash value with single quote although it wasn't necessary... – Mathieu Dumoulin Sep 07 '17 at 15:59
1

It's amazing that this was apparently a problem for so many people - myself included. This thing happens from time to time, but it seems kind of obscure. Ah well. Thanks – dgo Dec 07 '17 at 23:33
1

That was the issue for me. Thanks @jbrahy – colecmc Mar 01 '19 at 17:49
1

Yes I got the same. By removing space it worked well for me. – Amandeep kaur Jan 07 '20 at 12:30
1

Thanks " https://" cause error. use trim() to avoid such Error. – Ashish Sharma Aug 26 '20 at 11:48

score 53 · Answer 3 · answered Jan 14 '19 at 18:23

53

Looks like there are so many Answers already but the issue I faced was with double quotes. There is a difference in between:

“

and

Changing the 1 st double quote to the second worked for me, below is the sample curl:

curl -X PUT -u xxx:xxx -T test.txt "https://test.com/test/test.txt"

answered Jan 14 '19 at 18:23

Pavan_Obj

1,071
1
12
26

Sure thing my Man. – Pavan_Obj May 31 '19 at 20:41
This one fixed my problem. – Hari Ennekat Sep 26 '19 at 05:29
Glad it fixed :). – Pavan_Obj Sep 26 '19 at 19:52
fixed it for me too. Had not seen this error for other curl requests with https in the past so was wondering – Anupam Jul 27 '20 at 05:16
Good to know Anupam – Pavan_Obj Aug 04 '20 at 18:08

score 15 · Answer 4 · edited Feb 26 '13 at 16:31

15

I encountered the same problem while trying to install rvm for ruby. found the solution: after extracting curl (tar) in downloads folder of root.

cd /root/Downloads/curl # step-1
./configure --with-ssl # step-2
make # step-3
make install # step-4 (if not root, use sudo before command)

source

edited Feb 26 '13 at 16:31

answered Oct 09 '12 at 11:24

R T

4,369
3
38
49

score 13 · Answer 5 · edited May 31 '19 at 09:42

In my case, HTTPS protocol was not supported by libcurl at the first place. To find out which protocols are supported and which are not, I checked the curl version using command:

curl --version

It provided information as follows: curl 7.50.3 (x86_64-apple-darwin15.6.0) libcurl/7.50.3 SecureTransport zlib/1.2.5 Protocols: dict file ftp ftps gopher http imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Features: IPv6 Largefile NTLM NTLM_WB SSL libz UnixSockets

where https protocol happens to be not supported.

Then I re-installed curl and installed it using the following commands(after unpacked):

./configure --with-darwinssl (enable ssl communication in mac) make make test sudo make install

And after several minutes of work, Problems resolved!

Then I re-run the curl version command, it showed:

curl 7.50.3 (x86_64-apple-darwin15.6.0) libcurl/7.50.3 SecureTransport zlib/1.2.5 Protocols: dict file ftp ftps gopher http https imap imaps ldap ldaps pop3 pop3s rtsp smb smbs smtp smtps telnet tftp Features: IPv6 Largefile NTLM NTLM_WB SSL libz UnixSockets

HTTPS protocol showed up!

Finally, a useful site to refer when you run into curl problems. https://curl.haxx.se/docs/install.html

Aminah Nuraini · Answer 6 · 2016-04-25T02:03:22.973

12

I solve it just by changing 'http://webname...' to "http://webname..."

Notice the quote. It should be double (") instead of single (').

edited Apr 25 '16 at 02:03

answered Dec 02 '15 at 20:15

Aminah Nuraini

18,120
8
90
108

yes! This solved the issue for me, running curl in my windows command prompt. Thank you! – Ryano Aug 15 '19 at 01:09

Максим Мартынов · Answer 7 · 2019-02-18T12:17:40.560

10

Solved this problem with flag --with-darwinssl

Go to folder with curl source code

Download it here https://curl.haxx.se/download.html

sudo ./configure --with-darwinssl
make
make install

restart your console and it is done!

edited Feb 18 '19 at 12:17

answered Jun 22 '16 at 14:04

Максим Мартынов

1,197
13
13

Daniel Stenberg · Answer 8 · 2013-01-29T17:16:23.667

7

This is specifically mentioned in the libcurl FAQ entry "Protocol xxx not supported or disabled in libcurl".

For your pleasure I'm embedding the explanation here too:

When passing on a URL to curl to use, it may respond that the particular protocol is not supported or disabled. The particular way this error message is phrased is because curl doesn't make a distinction internally of whether a particular protocol is not supported (ie never got any code added that knows how to speak that protocol) or if it was explicitly disabled. curl can be built to only support a given set of protocols, and the rest would then be disabled or not supported.

Note that this error will also occur if you pass a wrongly spelled protocol part as in "htpt://example.com" or as in the less evident case if you prefix the protocol part with a space as in " http://example.com/".

edited Jan 29 '13 at 17:16

answered Sep 02 '11 at 06:49

Daniel Stenberg

54,736
17
146
222

23

I don't believe this answer explains to the OP what s/he needs to do to fix the problem. – isomorphismes Feb 16 '13 at 00:33
3

it explains what the message means, which implies that his command line wasn't enough to build libcurl with HTTPS enabled – Daniel Stenberg Feb 16 '13 at 12:58
Got bit by the space prefix. If only the error read 'Protocol "xxx" not supported or disabled in libcurl' – topher Jul 23 '14 at 16:15

SergA · Answer 9 · 2020-11-26T08:35:22.393

My problem was coused by not displayed UTF symbol. I copy the link from the browser (in my case it was an nginx track) and got the following in clipboard:

$ echo -n "https://sk.ee/upload/files/ESTEID-SK_2015.pem.crt" | hexdump -C
00000000  e2 80 8b 68 74 74 70 73  3a 2f 2f 73 6b 2e 65 65  |...https://sk.ee|
00000010  2f 75 70 6c 6f 61 64 2f  66 69 6c 65 73 2f 45 53  |/upload/files/ES|
00000020  54 45 49 44 2d 53 4b 5f  32 30 31 35 2e 70 65 6d  |TEID-SK_2015.pem|
00000030  2e 63 72 74                                       |.crt|

The problem is in the sequence 0xe2 0x80 0x8b, which precedes https. This sequence is a ZERO WIDTH JOINER encoded in UTF-8.

score 1 · Answer 10 · answered Aug 19 '15 at 17:55

1

Got the same error when using curl on https site like

curl https://api.dis...

as pointed out by ganesh, it was because my version of curl wasn't ssl enabled. went back and downloaded the version with ssl and it worked fine.

answered Aug 19 '15 at 17:55

Deepak Rao

11
1

2

So did I, didn't see the SSL option on the download page. – Patrick Borkowicz Oct 21 '15 at 14:43
how to install the ssl version on centos 7? – Awan Jul 21 '23 at 03:26

score 0 · Answer 11 · edited Mar 30 '16 at 02:21

I just recompiled curl with configure options pointing to the openssl 1.0.2g library folder and include folder, and I still get this message. When I do ldd on curl, it does not show that it uses either libcrypt.so or libssl.so, so I assume this must mean that even though the make and make install succeeded without errors, nevertheless curl does not have HTTPS support? Configure and make was as follows:

./configure --prefix=/local/scratch/PACKAGES/local --with-ssl=/local/scratch/PACKAGES/local/openssl/openssl-1.0.2g --includedir=/local/scratch/PACKAGES/local/include/openssl/openssl-1.0.2g
make
make test
make install

I should mention that libssl.so.1 is in /local/scratch/PACKAGES/local/lib. It is unclear whether the --with-ssl option should point there or to the directory where the openssl install placed the openssl.cnf file. I chose the latter. But if it were supposed to be the former, the make should have failed with an error that it couldn't find the library.

The link text itself is correct. curl cannot retrieve using https, and I don't know why. — tedtoal, Mar 30 '16 at 16:40

ntt · Answer 12 · 2017-02-16T17:35:55.550

0

Specifying the protocol within the url might solve your problem.

I had a similar problem (while using curl php client) :

I was passing domain.com instead of sftp://domain.com which lead to this confusing error:

Protocol "http" not supported or disabled in libcurl, took 0 seconds.

edited Feb 16 '17 at 17:35

answered Feb 16 '17 at 17:25

ntt

426
1
4
9

score 0 · Answer 13 · answered Apr 21 '23 at 19:18

0

to build CURL, you need ssl library first, so the curl binary can run with SSL embedded

Ok, let's go:

apt install libssl-dev
wget https://curl.se/download/curl-7.52.1.zip
unzip curl-7.52.1.zip
cd curl-7.52.1
make
make install

answered Apr 21 '23 at 19:18

PYK

3,674
29
17

curl : (1) Protocol https not supported or disabled in libcurl

13 Answers13

Linked

Related