blocks|key|1031744|text|您可以尝试安装演示证书(一些ssl提供商提供一个月的免费证书)，以确定问题是否与证书有效性有关。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1031745|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

You can try to install a demo certificate (some ssl providers offers them for free for a month) to be sure if the problem is related to cert validity or not.

blocks|key|1031795|text|您遇到的问题是aspNet用户没有访问证书的权限。您必须使用winhttpcertcfg.exe授予访问权限|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1031796|有关如何设置此设置的示例，请参阅：http://support.microsoft.com/kb/901183|offset|length|1031797|在更多信息中的步骤2下|1031798|编辑:在较新版本的IIS中，此功能内置于证书管理器工具中-可以通过右键单击证书并使用用于管理私钥的选项进行访问。更多详细信息请访问：https://serverfault.com/questions/131046/how-to-grant-iis-7-5-access-to-a-certificate-in-certificate-store/132791#132791|1031799|entityMap|0|LINK|mutability|MUTABLE|url|http://support.microsoft.com/kb/901183|1|https://serverfault.com/questions/131046/how-to-grant-iis-7-5-access-to-a-certificate-in-certificate-store/132791#132791^0|0|H|12|0|0|0|1U|3C|1|0^^$0|@$1|2|3|4|5|6|7|T|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|U|8|@]|9|@$D|V|E|W|1|X]]|A|$]]|$1|F|3|G|5|6|7|Y|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|Z|8|@]|9|@$D|10|E|11|1|12]]|A|$]]|$1|J|3|-4|5|6|7|13|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q]]|R|$5|M|N|O|A|$P|S]]]]

The problem you're having is that the aspNet user doesn't have access to the certificate. You have to give access using the winhttpcertcfg.exe

An example on how to set this up is at:
<a href="http://support.microsoft.com/kb/901183" rel="noreferrer">http://support.microsoft.com/kb/901183</a>

Under step 2 in more information

EDIT: In more recent versions of IIS, this feature is built in to the certificate manager tool - and can be accessed by right clicking on the certificate and using the option for managing private keys. More details here: <a href="https://serverfault.com/questions/131046/how-to-grant-iis-7-5-access-to-a-certificate-in-certificate-store/132791#132791">https://serverfault.com/questions/131046/how-to-grant-iis-7-5-access-to-a-certificate-in-certificate-store/132791#132791</a>

blocks|key|1031835|text|该错误是一般性的，SSL/TLS协商可能失败的原因有很多。最常见的是无效或过期的服务器证书，您可以通过提供自己的服务器证书验证挂钩来解决这个问题，但这不一定是唯一的原因。服务器可能需要相互身份验证，它可能配置了客户端不支持的密码套件，它可能具有太大的时间漂移而无法成功握手，以及更多原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1031836|最佳解决方案是使用SChannel故障排除工具集。SChannel是负责SSL和TLS的SSPI提供者，您的客户端将使用它进行握手。看看TLS/SSL+Tools+and+Settings吧。|offset|length|1031837|另请参阅How+to+enable+Schannel+event+logging。|1031838|entityMap|0|LINK|mutability|MUTABLE|url|http://technet.microsoft.com/en-us/library/cc776467%2528WS.10%2529.aspx|1|http://support.microsoft.com/kb/260729^0|0|1W|Q|0|0|4|10|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@$D|T|E|U|1|V]]|A|$]]|$1|F|3|G|5|6|7|W|8|@]|9|@$D|X|E|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

The error is generic and there are many reasons why the SSL/TLS negotiation may fail. The most common is an invalid or expired server certificate, and you took care of that by providing your own server certificate validation hook, but is not necessarily the only reason. The server may require mutual authentication, it may be configured with a suites of ciphers not supported by your client, it may have a time drift too big for the handshake to succeed and many more reasons. 

The best solution is to use the SChannel troubleshooting tools set. SChannel is the SSPI provider responsible for SSL and TLS and your client will use it for the handshake. Take a look at <a href="http://technet.microsoft.com/en-us/library/cc776467%28WS.10%29.aspx" rel="noreferrer">TLS/SSL Tools and Settings</a>.

Also see <a href="http://support.microsoft.com/kb/260729" rel="noreferrer">How to enable Schannel event logging</a>.

blocks|key|1031931|text|另一种可能性是盒子上的证书输入不正确。确保选中环绕复选框。最初我没有这样做，所以代码要么超时，要么抛出相同的异常，因为找不到私钥。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1031932|​|1031933|📷|atomic|offset|length|1031934|1031935|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/02f6a36f566a504fa5f341d8140e3e21.jpeg|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Another possibility is improper certificate importation on the box. Make sure to select encircled check box. Initially I didn't do it, so code was either timing out or throwing same exception as private key could not be located.

<img src="https://i.stack.imgur.com/0lMgD.jpg" alt="certificate importation dialog">

blocks|key|1247008|text|正如你所说的，有很多原因可能会发生。我想我会加上我遇到的原因...|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1247009|如果将WebRequest.Timeout的值设置为0，则会抛出此异常。下面是我的代码...(除了我有一个无意中设置为0的参数，而不是硬编码的0作为超时值)。|offset|length|style|CODE|1247010|WebRequest+webRequest+=+WebRequest.Create(@"https://myservice/path");
webRequest.ContentType+=+"text/html";
webRequest.Method+=+"POST";
string+body+=+"...";
byte[]+bytes+=+Encoding.ASCII.GetBytes(body);
webRequest.ContentLength+=+bytes.Length;
var+os+=+webRequest.GetRequestStream();
os.Write(bytes,+0,+bytes.Length);
os.Close();
webRequest.Timeout+=+0;+//setting+the+timeout+to+0+causes+the+request+to+fail
WebResponse+webResponse+=+webRequest.GetResponse();+//Exception+thrown+here+...|code-block|syntax|javascript|1247011|entityMap^0|0|3|I|Q|1|1N|1|1Z|1|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]|$D|S|E|T|F|G]|$D|U|E|V|F|G]|$D|W|E|X|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|Y|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|N|$]]

As you can tell there are plenty of reasons this might happen. Thought I would add the cause I encountered ... 

If you set the value of <code>WebRequest.Timeout</code> to <code>0</code>, this is the exception that is thrown. Below is the code I had... (Except instead of a hard-coded <code>0</code> for the timeout value, I had a parameter which was inadvertently set to <code>0</code>).

<pre><code>WebRequest webRequest = WebRequest.Create(@"https://myservice/path");
webRequest.ContentType = "text/html";
webRequest.Method = "POST";
string body = "...";
byte[] bytes = Encoding.ASCII.GetBytes(body);
webRequest.ContentLength = bytes.Length;
var os = webRequest.GetRequestStream();
os.Write(bytes, 0, bytes.Length);
os.Close();
webRequest.Timeout = 0; //setting the timeout to 0 causes the request to fail
WebResponse webResponse = webRequest.GetResponse(); //Exception thrown here ...
</code></pre>

blocks|key|1032010|text|我在尝试访问https://ct.mob0.com/Styles/Fun.png时遇到了这个问题，这是一个由CloudFlare在其CDN上分发的图像，它支持像SPDY和奇怪的重定向SSL证书这样的疯狂东西。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1032011|我没有像在Simons+answer中那样指定Ssl3，而是能够通过如下方式进入Tls12来修复它：|1032012|ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Tls12;
new+WebClient().DownloadData("https://ct.mob0.com/Styles/Fun.png");|code-block|syntax|javascript|1032013|entityMap|0|LINK|mutability|MUTABLE|url|https://ct.mob0.com/Styles/Fun.png^0|6|Y|0|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@$A|T|B|U|1|V]]|C|$]]|$1|D|3|E|5|6|7|W|8|@]|9|@]|C|$]]|$1|F|3|G|5|H|7|X|8|@]|9|@]|C|$I|J]]|$1|K|3|-4|5|6|7|Y|8|@]|9|@]|C|$]]]|L|$M|$5|N|O|P|C|$Q|R]]]]

I had this problem trying to hit <a href="https://ct.mob0.com/Styles/Fun.png" rel="noreferrer">https://ct.mob0.com/Styles/Fun.png</a>, which is an image distributed by CloudFlare on its CDN that supports crazy stuff like SPDY and weird redirect SSL certs.
Instead of specifying Ssl3 as in Simons answer I was able to fix it by going down to Tls12 like this:
<pre><code>ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
new WebClient().DownloadData(&quot;https://ct.mob0.com/Styles/Fun.png&quot;);
</code></pre>

blocks|key|1247206|text|只要这是一个相对“实时”的链接，我想我应该添加一个新的选项。这种可能性是，由于Poodle攻击的问题，该服务不再支持SSL+3.0。看看谷歌在这方面的声明。我在几个web服务中同时遇到了这个问题，并意识到必须发生一些事情。我切换到TLS+1.2，一切都恢复正常。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1247207|http://googleonlinesecurity.blogspot.com/2014/10/this-poodle-bites-exploiting-ssl-30.html|offset|length|1247208|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|2H|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|N|8|@]|9|@$D|O|E|P|1|Q]]|A|$]]|$1|F|3|-4|5|6|7|R|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|C]]]]

As long as this is a relatively "live" link I thought I would add a new option. That possibility is that the service is no longer supporting SSL 3.0 due to the problem with the Poodle attack. Check out the Google statement on this. I encountered this problem with several web services at once and realized something had to be going on. I switched to TLS 1.2 and everything is working again.

<a href="http://googleonlinesecurity.blogspot.com/2014/10/this-poodle-bites-exploiting-ssl-30.html" rel="nofollow">http://googleonlinesecurity.blogspot.com/2014/10/this-poodle-bites-exploiting-ssl-30.html</a>

blocks|key|1032202|text|经过长时间的解决同样的问题，我发现运行客户端服务的ASP.NET帐户没有访问证书的权限。我修复了它，进入运行web应用程序的IIS应用程序池，进入高级设置，并将身份从NetworkService更改为LocalSystem帐户。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1032203|一个更好的解决方案是让证书与默认的NetworkService帐户一起工作，但这对于快速功能测试是有效的。|1032204|entityMap^0|2B|E|2S|B|0|H|E|0^^$0|@$1|2|3|4|5|6|7|J|8|@$9|K|A|L|B|C]|$9|M|A|N|B|C]]|D|@]|E|$]]|$1|F|3|G|5|6|7|O|8|@$9|P|A|Q|B|C]]|D|@]|E|$]]|$1|H|3|-4|5|6|7|R|8|@]|D|@]|E|$]]]|I|$]]

After many long hours with this same issue I found that the ASP.NET account the client service was running under didn't have access to the certificate. I fixed it by going into the IIS Application Pool that the web app runs under, going into Advanced Settings, and changing the Identity to the <code>LocalSystem</code> account from <code>NetworkService</code>.

A better solution is to get the certificate working with the default <code>NetworkService</code> account but this works for quick functional testing.

blocks|key|1247394|text|对我来说，问题是我试图将IIS作为web服务部署，我在服务器上安装了证书，但运行IIS的用户对证书没有正确的权限。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1247395|How+to+give+ASP.NET+access+to+a+private+key+in+a+certificate+in+the+certificate+store?|offset|length|1247396|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/questions/2609859/how-to-give-asp-net-access-to-a-private-key-in-a-certificate-in-the-certificate^0|0|0|2E|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|O|8|@]|9|@$D|P|E|Q|1|R]]|A|$]]|$1|F|3|-4|5|6|7|S|8|@]|9|@]|A|$]]]|G|$H|$5|I|J|K|A|$L|M]]]]

The issue for me was that I was trying to deploy on IIS as a web service, I installed the certificate on the server, but the user that runs IIS didn't have the correct permissions on the certificate.

<a href="https://stackoverflow.com/questions/2609859/how-to-give-asp-net-access-to-a-private-key-in-a-certificate-in-the-certificate">How to give ASP.NET access to a private key in a certificate in the certificate store?</a>

blocks|key|1032412|text|这只发生在我的一个网站上，结果它只有RC4密码可用。在之前的加固服务器的努力中，我已经禁用了RC4密码，一旦我重新启用这个密码，问题就解决了。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1032413|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This was happening for me on just one site, and it turns out that it only had the RC4 cipher available. In a prior effort to harden the server, I had disabled the RC4 cipher, once I re-enabled this the issue was solved.

blocks|key|1247530|text|一些原始答案没有的东西。我添加了更多的代码，使其防弹。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1247531|ServicePointManager.Expect100Continue+=+true;
++++++++ServicePointManager.DefaultConnectionLimit+=+9999;
++++++++ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Tls+%7C+SecurityProtocolType.Tls11+%7C+SecurityProtocolType.Tls12+%7C+SecurityProtocolType.Ssl3;|code-block|syntax|javascript|1247532|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Something the original answer didn't have. I added some more code to make it bullet proof.

<pre><code>ServicePointManager.Expect100Continue = true;
 ServicePointManager.DefaultConnectionLimit = 9999;
 ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls | SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12 | SecurityProtocolType.Ssl3;
</code></pre>

blocks|key|1247635|text|我有这个问题是因为我的web.config有：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1247636|<httpRuntime+targetFramework="4.5.2"+/>|code-block|syntax|javascript|1247637|而不是：|1247638|<httpRuntime+targetFramework="4.6.1"+/>|1247639|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I had this problem because my web.config had:

<pre><code>&lt;httpRuntime targetFramework="4.5.2" /&gt;
</code></pre>

and not:

<pre><code>&lt;httpRuntime targetFramework="4.6.1" /&gt;
</code></pre>

blocks|key|1247677|text|这个在MVC+webclient中对我来说很有效。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1247678|public+string+DownloadSite(string+RefinedLink)
{
++++try
++++{
++++++++Uri+address+=+new+Uri(RefinedLink);

++++++++ServicePointManager.ServerCertificateValidationCallback+=+delegate+{+return+true;+};
++++++++ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Ssl3;

++++++++System.Net.ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Tls11+%7C+SecurityProtocolType.Tls12;

++++++++using+(WebClient+webClient+=+new+WebClient())
++++++++{
++++++++++++var+stream+=+webClient.OpenRead(address);
++++++++++++using+(StreamReader+sr+=+new+StreamReader(stream))
++++++++++++{
++++++++++++++++var+page+=+sr.ReadToEnd();

++++++++++++++++return+page;
++++++++++++}
++++++++}

++++}
++++catch+(Exception+e)
++++{
++++++++log.Error("DownloadSite+-+error+Lin+=+"+%2B+RefinedLink,+e);
++++++++return+null;
++++}
}|code-block|syntax|javascript|1247679|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

This one is working for me in MVC webclient
<pre><code>public string DownloadSite(string RefinedLink)
{
 try
 {
 Uri address = new Uri(RefinedLink);

 ServicePointManager.ServerCertificateValidationCallback = delegate { return true; };
 ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3;

 System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls11 | SecurityProtocolType.Tls12;

 using (WebClient webClient = new WebClient())
 {
 var stream = webClient.OpenRead(address);
 using (StreamReader sr = new StreamReader(stream))
 {
 var page = sr.ReadToEnd();

 return page;
 }
 }

 }
 catch (Exception e)
 {
 log.Error(&quot;DownloadSite - error Lin = &quot; + RefinedLink, e);
 return null;
 }
}
</code></pre>

blocks|key|1247739|text|默认的.NET+ServicePointManager.SecurityProtocol使用SSLv3和TLS。如果您正在访问Apache服务器，那么有一个名为SSLProtocol的配置变量，它缺省为TLSv1.2。您可以将ServicePointManager.SecurityProtocol设置为使用您的web服务器支持的适当协议，或者更改您的Apache配置以允许像此SSLProtocolall这样的所有协议。|type|unstyled|depth|inlineStyleRanges|offset|length|style|CODE|entityRanges|data|1247740|entityMap|0|LINK|mutability|MUTABLE|url|https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslprotocol^0|8|10|28|B|35|10|59|E|59|B|0|0^^$0|@$1|2|3|4|5|6|7|N|8|@$9|O|A|P|B|C]|$9|Q|A|R|B|C]|$9|S|A|T|B|C]|$9|U|A|V|B|C]]|D|@$9|W|A|X|1|Y]]|E|$]]|$1|F|3|-4|5|6|7|Z|8|@]|D|@]|E|$]]]|G|$H|$5|I|J|K|E|$L|M]]]]

The default .NET <code>ServicePointManager.SecurityProtocol</code> uses SSLv3 and TLS. If you are accessing an Apache server, there is a config variable called <code>SSLProtocol</code> which defaults to TLSv1.2. You can either set the <code>ServicePointManager.SecurityProtocol</code> to use the appropriate protocol supported by your web server or change your Apache config to allow all protocols like this <a href="https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#sslprotocol" rel="nofollow noreferrer"><code>SSLProtocol</code></a><code>all</code>.

blocks|key|1032721|text|在.NET+4.5中，这个问题的解决方案是|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1032722|ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Tls12;|code-block|syntax|javascript|1032723|如果您没有.NET+4.5，那么可以使用|1032724|ServicePointManager.SecurityProtocol+=+(SecurityProtocolType)3072;|1032725|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

The solution to this, in .NET 4.5 is

<pre><code>ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
</code></pre>

If you don’t have .NET 4.5 then use

<pre><code>ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;
</code></pre>

blocks|key|1247818|text|如果从Visual+Studio运行代码，请尝试以管理员身份运行Visual+Studio。为我修复了这个问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1247819|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

If you are running your code from Visual Studio, try running Visual Studio as administrator. Fixed the issue for me.

blocks|key|1032852|text|为我解决了这个问题，将网络服务添加到权限。右键单击证书>所有任务>管理私钥...>添加...>添加“网络服务”。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1032853|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

This fixed for me, add Network Service to permissions.
Right click on the certificate > All Tasks > Manage Private Keys... > Add... > Add "Network Service".

blocks|key|1032907|text|我也遇到了同样的问题，我发现this+answer对我来说工作正常。密钥是3072。This+link提供了有关“3072”修复的详细信息。|type|unstyled|depth|inlineStyleRanges|entityRanges|offset|length|data|1032908|ServicePointManager.SecurityProtocol+=+(SecurityProtocolType)3072;

XmlReader+r+=+XmlReader.Create(url);
SyndicationFeed+albums+=+SyndicationFeed.Load(r);|code-block|syntax|javascript|1032909|在我的例子中，有两个提要需要修复：|1032910|https://www.fbi.gov/feeds/fbi-in-the-news/atom.xml
https://www.wired.com/feed/category/gear/latest/rss|1032911|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/48930280/7311767|1|https://social.msdn.microsoft.com/Forums/en-US/0674f3ad-b23a-430c-9037-3d8ff80543cd/the-request-was-aborted-could-not-create-ssltls-secure-channel^0|E|B|0|16|9|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@$A|X|B|Y|1|Z]|$A|10|B|11|1|12]]|C|$]]|$1|D|3|E|5|F|7|13|8|@]|9|@]|C|$G|H]]|$1|I|3|J|5|6|7|14|8|@]|9|@]|C|$]]|$1|K|3|L|5|F|7|15|8|@]|9|@]|C|$G|H]]|$1|M|3|-4|5|6|7|16|8|@]|9|@]|C|$]]]|N|$O|$5|P|Q|R|C|$S|T]]|U|$5|P|Q|R|C|$S|V]]]]

I was having this same issue and found <a href="https://stackoverflow.com/a/48930280/7311767">this answer</a> worked properly for me. The key is 3072. <a href="https://social.msdn.microsoft.com/Forums/en-US/0674f3ad-b23a-430c-9037-3d8ff80543cd/the-request-was-aborted-could-not-create-ssltls-secure-channel" rel="noreferrer">This link</a> provides the details on the '3072' fix.

<pre><code>ServicePointManager.SecurityProtocol = (SecurityProtocolType)3072;

XmlReader r = XmlReader.Create(url);
SyndicationFeed albums = SyndicationFeed.Load(r);
</code></pre>

In my case two feeds required the fix:

<pre><code>https://www.fbi.gov/feeds/fbi-in-the-news/atom.xml
https://www.wired.com/feed/category/gear/latest/rss
</code></pre>

blocks|key|1032948|text|确保在创建HttpWebRequest之前进行了ServicePointManager设置，否则它将无法工作。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1032949|作品：|1032950|ServicePointManager.Expect100Continue+=+true;
ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Tls
+++++++%7C+SecurityProtocolType.Tls11
+++++++%7C+SecurityProtocolType.Tls12
+++++++%7C+SecurityProtocolType.Ssl3;

HttpWebRequest+request+=+(HttpWebRequest)WebRequest.Create("https://google.com/api/")|code-block|syntax|javascript|1032951|失败：|1032952|HttpWebRequest+request+=+(HttpWebRequest)WebRequest.Create("https://google.com/api/")

ServicePointManager.Expect100Continue+=+true;
ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Tls
+++++++%7C+SecurityProtocolType.Tls11
+++++++%7C+SecurityProtocolType.Tls12
+++++++%7C+SecurityProtocolType.Ssl3;|1032953|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|F|7|Q|8|@]|9|@]|A|$G|H]]|$1|I|3|J|5|6|7|R|8|@]|9|@]|A|$]]|$1|K|3|L|5|F|7|S|8|@]|9|@]|A|$G|H]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

Make sure the ServicePointManager settings are made before the HttpWebRequest is created, else it will not work.
Works:
<pre><code>ServicePointManager.Expect100Continue = true;
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls
 | SecurityProtocolType.Tls11
 | SecurityProtocolType.Tls12
 | SecurityProtocolType.Ssl3;

HttpWebRequest request = (HttpWebRequest)WebRequest.Create(&quot;https://google.com/api/&quot;)
</code></pre>
Fails:
<pre><code>HttpWebRequest request = (HttpWebRequest)WebRequest.Create(&quot;https://google.com/api/&quot;)

ServicePointManager.Expect100Continue = true;
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls
 | SecurityProtocolType.Tls11
 | SecurityProtocolType.Tls12
 | SecurityProtocolType.Ssl3;
</code></pre>

blocks|key|1248037|text|我最近遇到了同样的问题。我的环境是在带有VB.NET的.NET+4.6.1下运行的。这就是我如何修复它的：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1248038|ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Ssl3
ServicePointManager.ServerCertificateValidationCallback+=+New+RemoteCertificateValidationCallback(AddressOf+util.ValidateServerCertificate)|code-block|syntax|javascript|1248039|util.ValidateServerCertificate函数是：|1248040|Public+Function+ValidateServerCertificate(ByVal+sender+As+Object,+ByVal+certificate+As+X509Certificate,+ByVal+chain+As+X509Chain,+ByVal+sslPolicyErrors+As+SslPolicyErrors)+As+Boolean
++++Return+True
End+Function|1248041|entityMap^0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|M|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|N|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|O|8|@]|9|@]|A|$]]|$1|I|3|J|5|D|7|P|8|@]|9|@]|A|$E|F]]|$1|K|3|-4|5|6|7|Q|8|@]|9|@]|A|$]]]|L|$]]

I ran into the same issue recently. My environment is running under .NET 4.6.1 with VB.NET. That is how I fixed it:

<pre><code>ServicePointManager.SecurityProtocol = SecurityProtocolType.Ssl3
ServicePointManager.ServerCertificateValidationCallback = New RemoteCertificateValidationCallback(AddressOf util.ValidateServerCertificate)
</code></pre>

and the util.ValidateServerCertificate function is:

<pre><code>Public Function ValidateServerCertificate(ByVal sender As Object, ByVal certificate As X509Certificate, ByVal chain As X509Chain, ByVal sslPolicyErrors As SslPolicyErrors) As Boolean
 Return True
End Function
</code></pre>

blocks|key|1033054|text|如果你不想，不容易，或者不能快速修补你的代码，你可以在框架中强制你的.NET代码使用TLS1.2。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1033055|这不是我的应用程序，但它帮助热修复了我们旧的.NET+4.5应用程序(运行在Server2008r2上)，以便再次与Paypal+Payflow网关一起工作。他们必须在6/25/18和7/8/18之间开始在payflow网关回调上强制连接到TLS+1.2。|1033056|详情：https://github.com/TheLevelUp/pos-tls-patcher下载：https://github.com/TheLevelUp/pos-tls-patcher/releases|offset|length|1033057|entityMap|0|LINK|mutability|MUTABLE|url|https://github.com/TheLevelUp/pos-tls-patcher|1|https://github.com/TheLevelUp/pos-tls-patcher/releases^0|0|0|3|19|0|1F|1I|1|0^^$0|@$1|2|3|4|5|6|7|R|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|S|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|T|8|@]|9|@$F|U|G|V|1|W]|$F|X|G|Y|1|Z]]|A|$]]|$1|H|3|-4|5|6|7|10|8|@]|9|@]|A|$]]]|I|$J|$5|K|L|M|A|$N|O]]|P|$5|K|L|M|A|$N|Q]]]]

If you don't want to, can't easily, or can't quickly patch your code, instead, you can force TLS 1.2 usage by your .NET code in the framework.

This isn't my app, but it helped hotfix our older .NET 4.5 app (running on Server 2008r2) to work again with Paypal Payflow Gateway. They must have started forcing connections over to TLS 1.2 on the payflow gateway callbacks between 6/25/18 and 7/8/18.

Details: <a href="https://github.com/TheLevelUp/pos-tls-patcher" rel="nofollow noreferrer">https://github.com/TheLevelUp/pos-tls-patcher</a>
Download: <a href="https://github.com/TheLevelUp/pos-tls-patcher/releases" rel="nofollow noreferrer">https://github.com/TheLevelUp/pos-tls-patcher/releases</a>

blocks|key|1248211|text|这个问题可能有很多答案，因为它是关于一般错误消息的。我们在一些服务器上遇到了这个问题，但我们的开发机器没有遇到这个问题。拔掉我们大部分的头发后，我们发现这是一个微软的bug。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1248212|https://support.microsoft.com/en-us/help/4458166/applications-that-rely-on-tls-1-2-strong-encryption-experience-connect|offset|length|1248213|本质上，MS假设您想要较弱的加密，但是操作系统被修补为只允许TLS+1.2，因此您会收到可怕的“请求已中止:无法创建SSL/TLS安全通道”。|1248214|有三种修复方法。|1248215|1)使用适当的更新修补操作系统：http://www.catalog.update.microsoft.com/Search.aspx?q=kb4458166|1248216|2)在app.config/web.config文件中添加设置。|1248217|3)添加在另一个答案中已经提到的注册表设置。|1248218|所有这些都在我发布的知识库文章中提到。|1248219|entityMap|0|LINK|mutability|MUTABLE|url|1|http://www.catalog.update.microsoft.com/Search.aspx?q=kb4458166^0|0|0|3B|0|0|0|0|G|1R|1|0|0|0|0^^$0|@$1|2|3|4|5|6|7|10|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|11|8|@]|9|@$D|12|E|13|1|14]]|A|$]]|$1|F|3|G|5|6|7|15|8|@]|9|@]|A|$]]|$1|H|3|I|5|6|7|16|8|@]|9|@]|A|$]]|$1|J|3|K|5|6|7|17|8|@]|9|@$D|18|E|19|1|1A]]|A|$]]|$1|L|3|M|5|6|7|1B|8|@]|9|@]|A|$]]|$1|N|3|O|5|6|7|1C|8|@]|9|@]|A|$]]|$1|P|3|Q|5|6|7|1D|8|@]|9|@]|A|$]]|$1|R|3|-4|5|6|7|1E|8|@]|9|@]|A|$]]]|S|$T|$5|U|V|W|A|$X|C]]|Y|$5|U|V|W|A|$X|Z]]]]

This question can have many answers since it's about a generic error message. We ran into this issue on some of our servers, but not our development machines. After pulling out most of our hair, we found it was a Microsoft bug.

<a href="https://support.microsoft.com/en-us/help/4458166/applications-that-rely-on-tls-1-2-strong-encryption-experience-connect" rel="nofollow noreferrer">https://support.microsoft.com/en-us/help/4458166/applications-that-rely-on-tls-1-2-strong-encryption-experience-connect</a>

Essentially, MS assumes you want weaker encryption, but the OS is patched to only allow TLS 1.2, so you receive the dreaded "The request was aborted: Could not create SSL/TLS secure channel."

There are three fixes. 

1) Patch the OS with the proper update: <a href="http://www.catalog.update.microsoft.com/Search.aspx?q=kb4458166" rel="nofollow noreferrer">http://www.catalog.update.microsoft.com/Search.aspx?q=kb4458166</a>

2) Add a setting to your app.config/web.config file.

3) Add a registry setting that was already mentioned in another answer.

All of these are mentioned in the knowledge base article I posted.

blocks|key|1033190|text|我在商店里和档案里都有证书。我尝试连接文件，得到了这个错误信息。当我使用商店里的那个的时候，它起作用了。我最好的猜测是，当我想要使用文件中的证书时，由于存储了证书而出现了某种冲突。(同一台机器上的另一个服务使用商店中的证书，我使用文件中的证书开发了一个不同的服务。在测试之前，它在dev上就像是一个护身符。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1033191|entityMap^0|0^^$0|@$1|2|3|4|5|6|7|D|8|@]|9|@]|A|$]]|$1|B|3|-4|5|6|7|E|8|@]|9|@]|A|$]]]|C|$]]

I had cert in store and on file. I tried to connect with file and got this error message. When I used the one in the store it worked. My best guess is that some sort of conflict arose as a result of the cert being in store when I wanted to use the one on file.
(A different service on the same machine used the cert in store and I had developed a different service using the cert on file. Worked like a charm on dev until test).

blocks|key|1033238|text|我在通过命令行应用程序将视频上传到Wistia时遇到了这个问题。我们的系统管理员使用SSL+labs扫描upload.wistia.com中列出的IIScrypto启用了其他密码套件，从而解决了此问题。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1033239|TLS_DHE_RSA_WITH_AES_128_GCM_SHA256+(0x9e)+DH+2048位FS+128+TLS_DHE_RSA_WITH_AES_256_GCM_SHA384+(0x9f)+DH+2048位FS+256|1033240|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

I had this issue uploading a video to Wistia via a command line app. Our system administrator resolved the issue by enabling additional cipher suites using IIScrypto that was listed in the SSL labs scan for upload.wistia.com

TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) DH 2048 bits FS 128
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) DH 2048 bits FS 256

blocks|key|1033289|text|设置的方法|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1033290|ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Tls12|code-block|syntax|javascript|1033291|似乎还可以，因为Tls1.2是安全协议的最新版本。但我决定更深入地研究，并回答我们真的需要硬编码它。|1033292|规格:+Windows+Server+2012R2+x64。|1033293|从互联网上得知，.NetFramework+4.6%2B在默认情况下必须使用Tls1.2。但是当我将我的项目更新到4.6版本时，什么也没有发生。我找到了一些信息，这些信息告诉我需要手动进行一些更改才能默认启用Tls1.2|1033294|https://support.microsoft.com/en-in/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi|offset|length|1033295|但是建议的windows更新不适用于R2版本|1033296|但对我有帮助的是将2个值添加到注册表。您可以使用下一个PS脚本，以便自动添加它们|1033297|Set-ItemProperty+-Path+'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319'+-Name+'SchUseStrongCrypto'+-Value+'1'+-Type+DWord
Set-ItemProperty+-Path+'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319'+-Name+'SchUseStrongCrypto'+-Value+'1'+-Type+DWord|1033298|这就是我要找的东西。但是我仍然不能回答为什么NetFramework+4.6%2B不自动设置这个...Protocol值？|1033299|entityMap|0|LINK|mutability|MUTABLE|url^0|0|0|0|0|0|0|3B|0|0|0|0|0|0^^$0|@$1|2|3|4|5|6|7|15|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|16|8|@]|9|@]|A|$E|F]]|$1|G|3|H|5|6|7|17|8|@]|9|@]|A|$]]|$1|I|3|J|5|6|7|18|8|@]|9|@]|A|$]]|$1|K|3|L|5|6|7|19|8|@]|9|@]|A|$]]|$1|M|3|N|5|6|7|1A|8|@]|9|@$O|1B|P|1C|1|1D]]|A|$]]|$1|Q|3|R|5|6|7|1E|8|@]|9|@]|A|$]]|$1|S|3|T|5|6|7|1F|8|@]|9|@]|A|$]]|$1|U|3|V|5|D|7|1G|8|@]|9|@]|A|$E|F]]|$1|W|3|X|5|6|7|1H|8|@]|9|@]|A|$]]|$1|Y|3|-4|5|6|7|1I|8|@]|9|@]|A|$]]]|Z|$10|$5|11|12|13|A|$14|N]]]]

The approach with setting 

<pre><code>ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12
</code></pre>

Seems to be okay, because Tls1.2 is latest version of secure protocol. But I decided to look deeper and answer do we really need to hardcode it.

Specs: Windows Server 2012R2 x64.

From the internet there is told that .NetFramework 4.6+ must use Tls1.2 by default. But when I updated my project to 4.6 nothing happened.
I have found some info that tells I need manually do some changes to enable Tls1.2 by default 

<a href="https://support.microsoft.com/en-in/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi" rel="noreferrer">https://support.microsoft.com/en-in/help/3140245/update-to-enable-tls-1-1-and-tls-1-2-as-default-secure-protocols-in-wi</a>

But proposed windows update doesnt work for R2 version

But what helped me is adding 2 values to registry. You can use next PS script so they will be added automatically 

<pre><code>Set-ItemProperty -Path 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
Set-ItemProperty -Path 'HKLM:\SOFTWARE\Microsoft\.NetFramework\v4.0.30319' -Name 'SchUseStrongCrypto' -Value '1' -Type DWord
</code></pre>

That is kind of what I was looking for. But still I cant answer on question why NetFramework 4.6+ doesn't set this ...Protocol value automatically?

blocks|key|1248450|text|另一种可能是正在执行的代码没有所需的预留权限。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1248451|在我的例子中，当使用Visual+Studio调试器测试对web服务的调用时，我得到了这个错误。Visual+Studio未以管理员身份运行，这导致了此异常。|1248452|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|F|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|G|8|@]|9|@]|A|$]]|$1|D|3|-4|5|6|7|H|8|@]|9|@]|A|$]]]|E|$]]

Another possibility is that the code being executed doesn't have the required premissions.

In my case, I got this error when using Visual Studio debugger to test a call to a web service. Visual Studio wasn't running as Administrator, which caused this exception.

blocks|key|1033449|text|我在Windows2008Server上的.NET+4.5.2+Winform应用程序上也遇到了同样的错误。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1033450|我尝试了以下修复方法：|1033451|ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Tls1%7CSecurityProtocolType.Tls11%7C+SecurityProtocolType.Tls12;|offset|length|style|CODE|1033452|但这并不起作用，错误的发生次数仍然存在。|1033453|根据上面的答案之一，是否强制覆盖注册表的SchUseStrongCrypto项。如果我设置这个键，有什么副作用吗？|1033454|Windows+Registry+Editor+Version+5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
"SchUseStrongCrypto"=dword:00000001|code-block|syntax|javascript|1033455|entityMap^0|0|0|0|3C|0|0|0|0^^$0|@$1|2|3|4|5|6|7|U|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|V|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|W|8|@$F|X|G|Y|H|I]]|9|@]|A|$]]|$1|J|3|K|5|6|7|Z|8|@]|9|@]|A|$]]|$1|L|3|M|5|6|7|10|8|@]|9|@]|A|$]]|$1|N|3|O|5|P|7|11|8|@]|9|@]|A|$Q|R]]|$1|S|3|-4|5|6|7|12|8|@]|9|@]|A|$]]]|T|$]]

I have been getting the same error on a .NET 4.5.2 Winform application on a Windows 2008 Server.
I tried the following fix:
<code>ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls1|SecurityProtocolType.Tls11| SecurityProtocolType.Tls12;</code>
But that didnt work and the number of occurences of the error were still there.
As per one of the answers above, Is it mandatory to override the SchUseStrongCrypto key to the registry. Are there any side effects if i set this key.
<pre><code>Windows Registry Editor Version 5.00
[HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\.NETFramework\v4.0.30319]
&quot;SchUseStrongCrypto&quot;=dword:00000001
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\.NETFramework\v4.0.30319]
&quot;SchUseStrongCrypto&quot;=dword:00000001
</code></pre>

blocks|key|1033510|text|这样做对我很有帮助：|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1033511|System.Net.ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Tls12;|code-block|syntax|javascript|1033512|entityMap^0|0|0^^$0|@$1|2|3|4|5|6|7|I|8|@]|9|@]|A|$]]|$1|B|3|C|5|D|7|J|8|@]|9|@]|A|$E|F]]|$1|G|3|-4|5|6|7|K|8|@]|9|@]|A|$]]]|H|$]]

Doing this helped me:
<pre><code>System.Net.ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;
</code></pre>

blocks|key|1033564|text|从注册表中删除此选项帮助我在Windows+Server+2012+[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangAlgorithms中|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1033565|​|1033566|📷|atomic|offset|length|1033567|1033568|entityMap|0|IMAGE|mutability|IMMUTABLE|imageUrl|https://ask.qcloudimg.com/http-save/yehe-900000/e012d3fa7307e34df5102cfa8a8a60a8.png|imageAlt^0|0|0|0|1|0|0|0^^$0|@$1|2|3|4|5|6|7|S|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|T|8|@]|9|@]|A|$]]|$1|D|3|E|5|F|7|U|8|@]|9|@$G|V|H|W|1|X]]|A|$]]|$1|I|3|C|5|6|7|Y|8|@]|9|@]|A|$]]|$1|J|3|-4|5|6|7|Z|8|@]|9|@]|A|$]]]|K|$L|$5|M|N|O|A|$P|Q|R|-4]]]]

Delete this option from registry helped me in Windows Server 2012
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL\KeyExchangAlgorithms
<a href="https://i.stack.imgur.com/qTQWE.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/qTQWE.png" alt="enter image description here" /></a>

blocks|key|1033648|text|对于SOAP/WCF用户，当服务器拒绝您的WS-Security配置时，也会发生此错误。客户端收到的错误信息非常模糊，但服务器管理员很可能能够确定原因。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1033649|例如，在UsernameToken配置文件下，由于格式错误、不是通用协调时或服务器时间不匹配，<wsu:Created>时间被视为过期的消息不是有效的ISO8601日期时间。|offset|length|style|CODE|1033650|<wsse:UsernameToken+wsu:Id="Example-1">
+++<wsse:Username>+...+</wsse:Username>
+++<wsse:Password+Type="...">+...+</wsse:Password>
+++<wsse:Nonce+EncodingType="...">+...+</wsse:Nonce>
+++<wsu:Created>2021-01-31T19:00:00.0000000Z</wsu:Created>
</wsse:UsernameToken>|code-block|syntax|javascript|1033651|entityMap^0|0|1B|D|0|0^^$0|@$1|2|3|4|5|6|7|O|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|P|8|@$D|Q|E|R|F|G]]|9|@]|A|$]]|$1|H|3|I|5|J|7|S|8|@]|9|@]|A|$K|L]]|$1|M|3|-4|5|6|7|T|8|@]|9|@]|A|$]]]|N|$]]

For SOAP/WCF users, this error can also occur when the server rejects your WS-Security configuration. The error information the client receives is very vague, but the server administrator will likely be able to determine the reason.
Once example of this is under the UsernameToken Profile, where the message is considered expired by the <code>&lt;wsu:Created&gt;</code> time is not a valid ISO 8601 datetime, either due to bad formatting, not being UTC, or having mismatched server times.
<pre class="lang-xml prettyprint-override"><code>&lt;wsse:UsernameToken wsu:Id=&quot;Example-1&quot;&gt;
 &lt;wsse:Username&gt; ... &lt;/wsse:Username&gt;
 &lt;wsse:Password Type=&quot;...&quot;&gt; ... &lt;/wsse:Password&gt;
 &lt;wsse:Nonce EncodingType=&quot;...&quot;&gt; ... &lt;/wsse:Nonce&gt;
 &lt;wsu:Created&gt;2021-01-31T19:00:00.0000000Z&lt;/wsu:Created&gt;
&lt;/wsse:UsernameToken&gt;
</code></pre>

blocks|key|1248750|text|终于为我找到了解决方案。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1248751|在调用https+url+(对于.Net+Framework4.5)之前尝试添加下面这行：|1248752|ServicePointManager.SecurityProtocol+=+SecurityProtocolType.Tls12；|1248753|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|$]]

Finally found solution for me.
Try this adding below line before calling https url (for .Net framework 4.5):
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;

blocks|key|1248823|text|上面的大多数答案都提到了会话算法或密钥交换算法。|type|unstyled|depth|inlineStyleRanges|entityRanges|data|1248824|在我的例子中，两者都是正常的，问题出在服务器的证书散列算法中，客户端的PC上没有启用该算法。|1248825|我解决了这个问题，在应用程序的配置中添加了一个部分。|1248826|<system.diagnostics>
++++<trace+autoflush="true"+/>
++++<sources>
++++++++<source+name="System.Net">
++++++++++++<listeners>
++++++++++++++++<add+name="System.Net"+/>
++++++++++++</listeners>
++++++++</source>
++++++++<source+name="System.Net.Sockets">
++++++++++++<listeners>
++++++++++++++++<add+name="System.Net"+/>
++++++++++++</listeners>
++++++++</source>
++++++++<source+name="System.Net.Cache">
++++++++++++<listeners>
++++++++++++++++<add+name="System.Net"+/>
++++++++++++</listeners>
++++++++</source>
++++</sources>
++++<sharedListeners>
++++++++<add
++++++++++++name="System.Net"
++++++++++++type="System.Diagnostics.TextWriterTraceListener"
++++++++++++initializeData="System.Net.trace.log"
++++++++/>
++++</sharedListeners>
++++<switches>
++++++++<add+name="System.Net"+value="Verbose"+/>
++++++++<add+name="System.Net.Sockets"+value="Verbose"+/>
++++++++<add+name="System.Net.Cache"+value="Verbose"+/>
++++</switches>
</system.diagnostics>|code-block|syntax|javascript|1248827|然后，日志中的错误将我引导至此solution|offset|length|1248828|entityMap|0|LINK|mutability|MUTABLE|url|https://stackoverflow.com/a/54523827/4818603^0|0|0|0|0|F|8|0|0^^$0|@$1|2|3|4|5|6|7|W|8|@]|9|@]|A|$]]|$1|B|3|C|5|6|7|X|8|@]|9|@]|A|$]]|$1|D|3|E|5|6|7|Y|8|@]|9|@]|A|$]]|$1|F|3|G|5|H|7|Z|8|@]|9|@]|A|$I|J]]|$1|K|3|L|5|6|7|10|8|@]|9|@$M|11|N|12|1|13]]|A|$]]|$1|O|3|-4|5|6|7|14|8|@]|9|@]|A|$]]]|P|$Q|$5|R|S|T|A|$U|V]]]]

Most answers above mention session algorithms or key exchange algorithms.
In my case both were OK and the problem was in server's certificate hash algorithm, that was not enabled on client's PC.
I figured it out adding a section to my application's config.
<pre><code>&lt;system.diagnostics&gt;
 &lt;trace autoflush=&quot;true&quot; /&gt;
 &lt;sources&gt;
 &lt;source name=&quot;System.Net&quot;&gt;
 &lt;listeners&gt;
 &lt;add name=&quot;System.Net&quot; /&gt;
 &lt;/listeners&gt;
 &lt;/source&gt;
 &lt;source name=&quot;System.Net.Sockets&quot;&gt;
 &lt;listeners&gt;
 &lt;add name=&quot;System.Net&quot; /&gt;
 &lt;/listeners&gt;
 &lt;/source&gt;
 &lt;source name=&quot;System.Net.Cache&quot;&gt;
 &lt;listeners&gt;
 &lt;add name=&quot;System.Net&quot; /&gt;
 &lt;/listeners&gt;
 &lt;/source&gt;
 &lt;/sources&gt;
 &lt;sharedListeners&gt;
 &lt;add
 name=&quot;System.Net&quot;
 type=&quot;System.Diagnostics.TextWriterTraceListener&quot;
 initializeData=&quot;System.Net.trace.log&quot;
 /&gt;
 &lt;/sharedListeners&gt;
 &lt;switches&gt;
 &lt;add name=&quot;System.Net&quot; value=&quot;Verbose&quot; /&gt;
 &lt;add name=&quot;System.Net.Sockets&quot; value=&quot;Verbose&quot; /&gt;
 &lt;add name=&quot;System.Net.Cache&quot; value=&quot;Verbose&quot; /&gt;
 &lt;/switches&gt;
&lt;/system.diagnostics&gt;
</code></pre>
And then error in log led me to this <a href="https://stackoverflow.com/a/54523827/4818603">solution</a>

We are unable to connect to an HTTPS server using <code>WebRequest</code> because of this error message:
<code>The request was aborted: Could not create SSL/TLS secure channel.</code>
We know that the server doesn't have a valid HTTPS certificate with the path used, but to bypass this issue, we use the following code that we've taken from another StackOverflow post:
<pre><code>private void Somewhere() {
 ServicePointManager.ServerCertificateValidationCallback += new RemoteCertificateValidationCallback(AlwaysGoodCertificate);
}

private static bool AlwaysGoodCertificate(object sender, X509Certificate certificate, X509Chain chain, SslPolicyErrors policyErrors) {
 return true;
}
</code></pre>
The problem is that server never validates the certificate and fails with the above error. Does anyone have any idea of what I should do?
<hr />
I should mention that a colleague and I performed tests a few weeks ago and it was working fine with something similar to what I wrote above. The only &quot;major difference&quot; we've found is that I'm using Windows 7 and he was using Windows XP. Does that change something?

The request was aborted: Could not create SSL/TLS secure channel

Windows Server

Visual Studio

身份验证

服务器

调试器

Windows

由于以下错误消息，我们无法使用WebRequest连接到HTTPS服务器：The request was aborted: Could not create SSL/TLS secure channel.我们知道服务器没有有效的HTTPS证书和使用的路径，但是为了绕过这个问题，我们使用了下面的代码，这些代码取自另一篇S...

问请求已中止:无法创建SSL/TLS安全通道
EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问请求已中止:无法创建SSL/TLS安全通道EN

社区

活动

资源

关于

腾讯云开发者

热门产品

热门推荐

更多推荐

问请求已中止:无法创建SSL/TLS安全通道
EN