blocks|key|323675|text|api.evercam.io证书中的通用名称是*.herokuapp.com，证书中没有其他的主题名称。这意味着api.evercam.io的证书与主机名不匹配，因此证书验证失败。与www.evercam.io相同，例如，使用浏览器尝试https://www.evercam.io，您将得到错误消息，即证书中的名称与主机名不匹配。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|323676|因此，这是一个需要evercam.io解决的问题。如果您不关心安全性、中间人攻击等，您可能会禁用证书的验证(curl+--insecure)，但是您应该问问自己为什么要使用https而不是http。|323677|entityMap|0|LINK|mutability|MUTABLE|url|https://www.evercam.io/^0|0|E|N|F|1K|E|2J|E|3A|M|0|0|1I|F|0^^$0|@$1|2|3|4|5|6|7|P|8|@$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]|$9|W|A|X|B|C]]|D|@$9|Y|A|Z|1|10]]|E|$]]|$1|F|3|G|5|6|7|11|8|@$9|12|A|13|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|14|8|@]|D|@]|E|$]]]|I|$J|$5|K|L|M|E|$N|O]]]]

The common name in the certicate for <code>api.evercam.io</code> is for <code>*.herokuapp.com</code> and there are no alternative subject names in the certificate. This means, that the certificate for <code>api.evercam.io</code> does not match the hostname and therefore the certificate verification fails.
Same as true for <code>www.evercam.io</code>, e.g. try <a href="https://www.evercam.io" rel="noreferrer">https://www.evercam.io</a> with a browser and you get the error message, that the name in the certificate does not match the hostname. 

So it is a problem which needs to be fixed by evercam.io. If you don't care about security, man-in-the-middle attacks etc you might disable verification of the certificate (<code>curl --insecure</code>), but then you should ask yourself why you use https instead of http at all.

blocks|key|2495062|text|当证书与主机名不匹配时，通常会发生这种情况。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2495063|解决方案是与主机联系并要求它修复其证书。|2495064|否则，可以关闭cURL对证书的验证，使用-k+(或--insecure)选项。|offset|length|style|CODE|2495065|请注意，正如选项所述，它是不安全的。您不应该使用此选项，因为它允许中间人攻击，并且挫败了HTTPS的目的。|2495066|在这里可以找到更多信息：http://curl.haxx.se/docs/sslcerts.html|2495067|entityMap|0|LINK|mutability|MUTABLE|url|http://curl.haxx.se/docs/sslcerts.html^0|0|0|K|2|P|A|0|0|C|12|0|0^^$0|@$1|2|3|4|5|6|7|V|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|W|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|X|8|@$F|Y|G|Z|H|I]|$F|10|G|11|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|12|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|13|8|@]|9|@$F|14|G|15|1|16]]|A|$]]|$1|N|3|-4|5|6|7|17|8|@]|9|@]|A|$]]]|O|$P|$5|Q|R|S|A|$T|U]]]]

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

The solution would be to contact the host and ask it to fix its certificate. 
Otherwise you can turn off cURL's verification of the certificate, use the <code>-k</code> (or <code>--insecure</code>) 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: <a href="http://curl.haxx.se/docs/sslcerts.html" rel="noreferrer">http://curl.haxx.se/docs/sslcerts.html</a>

blocks|key|2495101|text|编者按:如果您使用的PHP版本已经足够老到可以使用它，这是一种非常危险的方法。它向中间人攻击打开您的代码，并删除加密连接的主要目的之一。这样做的能力已经从PHP的现代版本中删除了，因为它太危险了。70次投票被否决的唯一原因是人们懒惰。别这么做。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|2495102|我知道这是一个(非常)古老的问题，而且是关于命令行的，但是当我在Google上搜索"SSL:没有替代的证书主题名称与目标主机名匹配“时，这是第一次成功。|2495103|我花了很长时间才找到答案，所以希望这能节省很多时间！在PHP中，将其添加到cUrl+setopts中：|2495104|curl_setopt($curl,+CURLOPT_SSL_VERIFYHOST,+FALSE);
curl_setopt($curl,+CURLOPT_SSL_VERIFYPEER,+FALSE);|code-block|syntax|javascript|2495105|这应该是暂时的解决办法。既然这是证书错误，当然最好是把证书修好！|2495106|entityMap^0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Q|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|R|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|S|8|@]|9|@]|A|$]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

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

<hr>

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 me a good while to figure out the answer so hope this saves someone a lot of time! 
In PHP add this to your cUrl setopts:

<pre><code>curl_setopt($curl, CURLOPT_SSL_VERIFYHOST, FALSE);
curl_setopt($curl, CURLOPT_SSL_VERIFYPEER, FALSE);
</code></pre>

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

blocks|key|323772|text|正如错误代码所述，“没有可供选择的证书主题名称与目标主机名匹配”--因此SSL证书存在问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|323773|证书应该包括SAN，并且只使用SAN。一些浏览器忽略不推荐的公共名称。|323774|RFC+2818明确指出：“如果存在subjectAltName扩展类型dNSName，则必须使用它作为标识。否则，必须使用证书主题字段中的(最具体的)通用名称字段。虽然使用公共名称是现有的做法，但不推荐使用该扩展，并鼓励证书颁发机构使用dNSName。”|323775|entityMap^0|0|0|0^^$0|@$1|2|3|4|5|6|7|H|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|I|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|J|8|@]|9|@]|A|$]]|$1|F|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|G|$]]

As the error code says, "no alternative certificate subject name matches target host name" - so there is an issue with the SSL certificate. 

The certificate should include SAN, and only SAN will be used. Some browsers ignore the deprecated Common Name.

RFC 2818 clearly states 
 "If a subjectAltName extension of type dNSName is present, that MUST
 be used as the identity. Otherwise, the (most specific) Common Name
 field in the Subject field of the certificate MUST be used. Although
 the use of the Common Name is existing practice, it is deprecated and
 Certification Authorities are encouraged to use the dNSName instead."

blocks|key|323782|text|我也有过同样的问题。在我的例子中，我使用的是数字海洋和nginx。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|323783|我首先在数字海洋中设置了域example.app和子域dev.exemple.app。第二，我从godaddy那里购买了两个ssl证书。最后，我在nginx中配置了两个域，用下面的代码片段使用这两个ssl证书|323784|我的example.app域配置|323785|++++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+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+serve+request+as+file,+then
++++++++++++#+as+directory,+then+fall+back+to+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;
++++}
+}|code-block|syntax|javascript|323786|我的dev.example.app|323787|+++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+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+serve+request+as+file,+then
++++++++++++#+as+directory,+then+fall+back+to+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;
++++}
+}|323788|当我启动https://dev.echantillonnage.app的时候，我|offset|length|323789|++++Fix+CURL+(51)+SSL+error:+no+alternative+certificate+subject+name+matches|323790|我的错误是这两条线|323791|++++listen+444+ssl+default_server;
+++++listen+[::]:444+ssl+default_server;|323792|我不得不把这个改成：|323793|+++++listen+443+ssl;
+++++listen+[::]:443+ssl;|323794|entityMap|0|LINK|mutability|MUTABLE|url|https://dev.echantillonnage.app/^0|0|0|0|0|0|0|4|V|0|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1A|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1B|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|1C|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|1D|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|1E|8|@]|9|@]|A|$]]|$1|M|3|N|5|H|7|1F|8|@]|9|@]|A|$I|J]]|$1|O|3|P|5|6|7|1G|8|@]|9|@$Q|1H|R|1I|1|1J]]|A|$]]|$1|S|3|T|5|H|7|1K|8|@]|9|@]|A|$I|J]]|$1|U|3|V|5|6|7|1L|8|@]|9|@]|A|$]]|$1|W|3|X|5|H|7|1M|8|@]|9|@]|A|$I|J]]|$1|Y|3|Z|5|6|7|1N|8|@]|9|@]|A|$]]|$1|10|3|11|5|H|7|1O|8|@]|9|@]|A|$I|J]]|$1|12|3|-4|5|6|7|1P|8|@]|9|@]|A|$]]]|13|$14|$5|15|16|17|A|$18|19]]]]

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

My example.app domain config 

<pre><code> 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 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 serve request as file, then
 # as directory, then fall back to 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;
 }
 }
</code></pre>

My dev.example.app

<pre><code> 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 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 serve request as file, then
 # as directory, then fall back to 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;
 }
 }
</code></pre>

When I was launching <a href="https://dev.echantillonnage.app" rel="nofollow noreferrer">https://dev.echantillonnage.app</a> , I was getting 

<pre><code> Fix CURL (51) SSL error: no alternative certificate subject name matches
</code></pre>

My mistake was the two lines bellow

<pre><code> listen 444 ssl default_server;
 listen [::]:444 ssl default_server;
</code></pre>

I had to change this to:

<pre><code> listen 443 ssl;
 listen [::]:443 ssl;
</code></pre>

blocks|key|825851|text|这可能会为某人节省一些时间。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|825852|如果您使用GuzzleHttp，并且面临以下错误消息:+cURL+error+60:+SSL:没有其他证书主题名称匹配目标主机名，并且您对“不安全”解决方案(不推荐用于生产)很满意，那么必须将\GuzzleHttp\RequestOptions::VERIFY+=>+false添加到客户端配置中：|offset|length|style|BOLD|CODE|825853|$this->client+=+new+\GuzzleHttp\Client([
++++'base_uri'++++++++++++++++++++++++++=>+'someAccessPoint',
++++\GuzzleHttp\RequestOptions::HEADERS+=>+[
++++++++'User-Agent'+=>+'some-special-agent',
++++],
++++'defaults'++++++++++++++++++++++++++=>+[
++++++++\GuzzleHttp\RequestOptions::CONNECT_TIMEOUT+=>+5,
++++++++\GuzzleHttp\RequestOptions::ALLOW_REDIRECTS+=>+true,
++++],
++++\GuzzleHttp\RequestOptions::VERIFY++=>+false,
]);|code-block|syntax|javascript|825854|，在CURLOPT_SSL_VERIFYHOST方法中将CURLOPT_SSL_VERIFYPEER设置为0，将CURLOPT_SSL_VERIFYPEER设置为false。|825855|$conf[CURLOPT_SSL_VERIFYHOST]+=+0;
$conf[CURLOPT_SSL_VERIFYPEER]+=+false;|825856|来自GuzzleHttp文档|825857|验证
描述请求的SSL证书验证行为。|blockquote|825858|设置为true以启用SSL证书验证，并使用操作系统提供的默认CA+>。|unordered-list-item|825859|设置为false以禁用证书验证(这是不安全的！)。|825860|设置为字符串以提供CA包的路径，以启用使用自定义证书的验证。|825861|entityMap|0|LINK|mutability|MUTABLE|url|http://docs.guzzlephp.org/en/stable/request-options.html#verify^0|0|5|A|2O|17|0|0|2|M|S|M|1K|M|0|0|2|C|0|0|0|2|0|0|0|0^^$0|@$1|2|3|4|5|6|7|1B|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|1C|8|@$D|1D|E|1E|F|G]|$D|1F|E|1G|F|H]]|9|@]|A|$]]|$1|I|3|J|5|K|7|1H|8|@]|9|@]|A|$L|M]]|$1|N|3|O|5|6|7|1I|8|@$D|1J|E|1K|F|H]|$D|1L|E|1M|F|H]|$D|1N|E|1O|F|H]]|9|@]|A|$]]|$1|P|3|Q|5|K|7|1P|8|@]|9|@]|A|$L|M]]|$1|R|3|S|5|6|7|1Q|8|@]|9|@$D|1R|E|1S|1|1T]]|A|$]]|$1|T|3|U|5|V|7|1U|8|@$D|1V|E|1W|F|G]]|9|@]|A|$]]|$1|W|3|X|5|Y|7|1X|8|@]|9|@]|A|$]]|$1|Z|3|10|5|Y|7|1Y|8|@]|9|@]|A|$]]|$1|11|3|12|5|Y|7|1Z|8|@]|9|@]|A|$]]|$1|13|3|-4|5|6|7|20|8|@]|9|@]|A|$]]]|14|$15|$5|16|17|18|A|$19|1A]]]]

it might save some time to somebody.

If you use GuzzleHttp and you face with this error message cURL error 60: SSL: no alternative certificate subject name matches target host name and you are fine with the 'insecure' solution (not recommended on production) then you have to add
<code>\GuzzleHttp\RequestOptions::VERIFY =&gt; false</code> to the client configuration:

<pre><code>$this-&gt;client = new \GuzzleHttp\Client([
 'base_uri' =&gt; 'someAccessPoint',
 \GuzzleHttp\RequestOptions::HEADERS =&gt; [
 'User-Agent' =&gt; 'some-special-agent',
 ],
 'defaults' =&gt; [
 \GuzzleHttp\RequestOptions::CONNECT_TIMEOUT =&gt; 5,
 \GuzzleHttp\RequestOptions::ALLOW_REDIRECTS =&gt; true,
 ],
 \GuzzleHttp\RequestOptions::VERIFY =&gt; false,
]);
</code></pre>

which sets <code>CURLOPT_SSL_VERIFYHOST</code> to 0 and <code>CURLOPT_SSL_VERIFYPEER</code> to false in the <code>CurlFactory::applyHandlerOptions()</code> method

<pre><code>$conf[CURLOPT_SSL_VERIFYHOST] = 0;
$conf[CURLOPT_SSL_VERIFYPEER] = false;
</code></pre>

From the <a href="http://docs.guzzlephp.org/en/stable/request-options.html#verify" rel="noreferrer">GuzzleHttp documentation</a>

<blockquote>
 verify
 
 Describes the SSL certificate verification behavior of a request.
 
 <ul>
 <li>Set to true to enable SSL certificate verification and use the default CA bundle > provided by operating system.</li>
 <li>Set to false to disable certificate verification (this is insecure!).</li>
 <li>Set to a string to provide the path to a CA bundle to enable verification using a custom certificate.</li>
 </ul>
</blockquote>

I am new to CURL world, coming from Windows + .NET domain.

Trying to access Rest API for basic authentication at <a href="http://www.evercam.io/docs/api/v1/authentication">http://www.evercam.io/docs/api/v1/authentication</a>.

<pre><code>curl -X GET https://api.evercam.io/v1/... \
-u {username}
</code></pre>

Don't know how to use this command on windows command prompt after having CURL setup successfully. Tested CURL as follows:

<pre><code>C:\&gt;curl --version
curl 7.33.0 (x86_64-pc-win32) libcurl/7.33.0 OpenSSL/0.9.8y zlib/1.2.8 libssh2/1.4.3
Protocols: dict file ftp ftps gopher http https imap imaps pop3 pop3s rtsp scp s
ftp smtp smtps telnet tftp
Features: AsynchDNS GSS-Negotiate Largefile NTLM SSL SSPI libz
</code></pre>

Now i am ending with this

<pre><code>C:\&gt;curl -u myuser:mypassword -X GET https://api.evercam.io/v1/
curl: (51) SSL: no alternative certificate subject name matches target host name 'api.evercam.io'
</code></pre>

How can I fix this SSL issue 51 error ?

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

翻译质量差，导致语言生硬或混乱。

没有提供实际的解决方法或示例。

解答不清晰，无法理解或解决问题。

页面排版不美观，阅读体验差。

文章

问答

视频

学习中心

腾讯云实验室

直播

竞赛

腾讯云代码分析专区

腾讯iOA零信任安全管理系统专区

腾讯云架构师技术同盟交流圈

腾讯云数据库专区

腾讯云顾问专区

腾讯云原生专区

腾讯混元专区

腾讯云TCE专区

腾讯云Lighthouse专区

腾讯云HAI专区

腾讯云Edgeone专区

腾讯云存储专区

腾讯云智能专区

腾讯轻联专区 

腾讯云开发专区

TAPD专区

腾讯轻量云游戏服专区

腾讯云最具价值专家

腾讯云架构师技术同盟

腾讯云创作之星

腾讯云开发者先锋 

腾讯云代码助手

CODING DevOps

Cloud Studio

SDK中心

API中心

命令行工具

我是新的卷曲世界，来自Windows + .NET领域。尝试访问Rest，以便在上进行基本身份验证。curl -X GET https://api.evercam.io/v1/... \-u {username}不知道如何在成功安装CURL之后在windows命令提示符上使用此命令。经测试的卷曲如下：C:\>curl ...

问Curl:修正CURL (51) SSL错误:没有可选证书主题名称匹配
EN

Stack Overflow用户

社区

活动

圈层

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问Curl:修正CURL (51) SSL错误:没有可选证书主题名称匹配EN