Curl: Fix CURL (51) SSL error: no alternative certificate subject name matches

asked Dec 30, 2013 at 15:59

theGeekstertheGeekster

6,23113 gold badges36 silver badges47 bronze badges

It usually happens when the certificate does not match with the host name.

The solution would be to tướng liên hệ the host and ask it to tướng fix its certificate.
Otherwise you can turn off cURL's verification of the certificate, use the -k (or --insecure) option.
Please note that as the option said, it is insecure. You shouldn't use this option because it allows man-in-the-middle attacks and defeats the purpose of HTTPS.

More can be found in here: http://curl.haxx.se/docs/sslcerts.html

Editor's note: this is a very dangerous approach, if you are using a version of PHP old enough to tướng use it. It opens your code to tướng man-in-the-middle attacks and removes one of the primary purposes of an encrypted connection. The ability to tướng bởi this has been removed from modern versions of PHP because it is sánh dangerous. The only reason this has been upvoted 70 time is because people are lazy. DO NOT DO THIS.

I know it's a (very) old question and it's about command line, but when I searched Google for "SSL: no alternative certificate subject name matches target host name", this was the first hit.

It took bu a good while to tướng figure out the answer sánh hope this saves someone a lot of time! In PHP add this to tướng your cUrl setopts:

curl_setopt($curl, CURLOPT_SSL_VERIFYHOST, FALSE);
curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, FALSE);

p.s: this should be a temporary solution. Since this is a certificate error, best thing is to tướng have the certificate fixed ofcourse!

answered May 10, 2019 at 14:34

Zoltán SüleZoltán Süle

1,65820 silver badges30 bronze badges

I had the same issue. In my case I was using digitalocean and nginx.
I have first setup a domain name example.ứng dụng and a subdomain dev.exemple.ứng dụng in digitalocean. Second,I purchased two ssl certificat from godaddy. And finaly, I configured two domain name in nginx to tướng use those two ssl certificat with the following snipet

My example.ứng dụng domain name config

    server {
    listen 7000 default_server;
    listen [::]:7000 default_server;

     listen 443 ssl default_server;
     listen [::]:443 ssl default_server;

    root /srv/nodejs/echantillonnage1;

    # Add index.php to tướng the list if you are using PHP
    index index.html index.htm index.nginx-debian.html;

    server_name echantillonnage.app;
    ssl_certificate /srv/nodejs/certificatSsl/widcardcertificate/echantillonnage.app.chained.crt;
    ssl_certificate_key /srv/nodejs/certificatSsl/widcardcertificate/echantillonnage.app.key;

    location / {
            # First attempt to tướng serve request as tệp tin, then
            # as directory, then fall back to tướng displaying a 404.
            proxy_pass http://127.0.0.1:8090;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection 'upgrade';
            proxy_set_header Host $host;
            proxy_cache_bypass $http_upgrade;
    #try_files $uri $uri/ =404;
    }
 }

My dev.example.app

   server {
    listen 7000 default_server;
    listen [::]:7000 default_server;

     listen 444 ssl default_server;
     listen [::]:444 ssl default_server;

    root /srv/nodejs/echantillonnage1;

    # Add index.php to tướng the list if you are using PHP
    index index.html index.htm index.nginx-debian.html;

    server_name dev.echantillonnage.app;
    ssl_certificate /srv/nodejs/certificatSsl/dev/dev.echantillonnage.app.chained.crt;
    ssl_certificate_key /srv/nodejs/certificatSsl/dev/dev.echantillonnage.app.key;

    location / {
            # First attempt to tướng serve request as tệp tin, then
            # as directory, then fall back to tướng displaying a 404.
            proxy_pass http://127.0.0.1:8091;
            proxy_http_version 1.1;
            proxy_set_header Upgrade $http_upgrade;
            proxy_set_header Connection 'upgrade';
            proxy_set_header Host $host;
            proxy_cache_bypass $http_upgrade;
    #try_files $uri $uri/ =404;
    }
 }

When I was launching https://dev.echantillonnage.ứng dụng , I was getting

    Fix CURL (51) SSL error: no alternative certificate subject name matches

My mistake was the two lines bellow

    listen 444 ssl default_server;
     listen [::]:444 ssl default_server;

I had to tướng change this to:

     listen 443 ssl;
     listen [::]:443 ssl;

answered Mar 26, 2019 at 9:17

AlexAlex

9839 silver badges9 bronze badges