This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(153.6, 26%, 24%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ES%3C/text%3E%3C/svg%3E)
.Net Class Library is based on 4.5 and using HtmlAgilityPack, I was calling an https URL and it was working fine.
After the website is updated and will not support old browsers which are not TLS v1.2 compliant. Getting the error -
The request was aborted: Could not create SSL/TLS secure channel
Tried below article, still it is not working
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 45%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
The linked article said that clearly - updated to v4.7+ will make it work by default. Is there any reason that prevents you to do so?
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 28.999999999999996%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EXZ%3C/text%3E%3C/svg%3E)
The SharePoint Server is installed on Windows Server 2012 R2 and the configuration as follows
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup>
In VS 2015, there is no option to upgrade to .NET Framework 4.7 and when i did it to .net 4.7 from another machine also the same error persist.
Tried all below option.Still unable to use HtmlAgilityPack. Please suggest
I upgraded to .Net Framework 4.7 from another machine. Still it did not work.
Hi @SGH ,
Considering that you may need to switch to Tls13, try to upgrade your app to .NET Framework 4.8 which has supported Tsl13.
ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls13;
In the code, I need to use this right ? - ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls13;
what about support runtime.
I tried the below options before. But it did not work.
Do I need to change anything in the App.Config
<configuration>
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
</startup>
From the Window Server 2012 R2, the solution is not working. But the same solution works in Windows 10 Machine if the target framework is .net framework 4.5.2
When we change target frame work to .net framework 4.8, and update the code with ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls13;
<startup>
<supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.8"/>
</startup>
Getting the following error in Windows 10 machine.
works in Windows 10 machine. But I need to run it from Windows Server 2012 R2 Machine. Please advise.
Pleas advise
In that case the only way would make it work would be to use the other SSL libraries. .NET framework uses SChannel to provide HTTPS encryption, however TLS1.3 is not supported on Win2012R2 version there. (In fact, as of now the only Windows version have TLS1.3 support is Win10. It's not supported on any of the Windows Server versions)
If the server have Chromium based Edge, you may also consider change to use WebView2 control instead because Chromium doesn't use SChannel either. If you want to choose this route, it's worthwhile to take a look at the WebView2Brower project that is created by the Edge team to create a browser solely with WebView2 control.
FYI, if we're talking about TLS 1.3, since SSL encryption of .NET Framework is provided by SChannel Windows Service, and currently only Win10 have TLS1.3 support (i.e.: none of the Windows Server version have TLS 1.3) you'll have to wait for an update for Windows Server 2019 and upgrade there in order to work. (I doubt if Microsoft will backport it to earlier system.)
If you need TLS1.3 support real fast, consider rewrite to use OpenSSL or other libraries instead.
Still I am using TLS 1.2 in the application from Windows 10 (not TLS 1.3) and it is working.
Can I use HtmlAgilityPack with OpenSSL ? do you have additional information ?
No, to use OpenSSL, you'll literally need to rewrite that part from scratch, so only do that if there is urgent need to use TLS 1.3. (Some sites such as devblogs.microsoft.com upgraded to allow TLS 1.3 only. So if I started Fiddler on Win7, I cannot access it with HTTPS decryption turned on)
This information is for the topic on TLS 1.3 only, not something directly related to your problem.
Follow the Premier Developer blog if you want to monitor the announcement of TLS1.3 support on servers.
Please find below the protocol and cipher supported by the URL
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
Hi I am using .Net Framework 4.7, but still I am getting same error. even I tried with .Net framework 4.8 but didn't work showing error as follows. Pls help me out.
The request was aborted: Could not create SSL/TLS secure channel.
__Description:__An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
__Exception Details:__System.Net.WebException: The request was aborted: Could not create SSL/TLS secure channel.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(243.2, 41%, 33%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ERF%3C/text%3E%3C/svg%3E)
In my situation, removing "request.Credentials = CredentialCache.DefaultCredentials" fixed the problem.