.NET TLS SSL / TLS Origin: Network OSI layer 6 · Presentation Last updated 18 Nov 2026

The request was aborted: Could not create SSL/TLS secure channel (.NET Framework TLS 1.2 not enabled)

An older .NET Framework app tries TLS 1.0/1.1 while the server requires TLS 1.2+.

Exact message you may see The request was aborted: Could not create SSL/TLS secure channelSystem.Net.WebException: The request was aborted: Could not create SSL/TLS secure channelThe underlying connection was closed: An unexpected error occurred on a sendAuthentication failed because the remote party has closed the transport stream
Seen on: .NET Windows SSL

Meaning

Target .NET 4.7+ (uses system defaults) or set ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12 (and Tls13 where available) early in startup, and enable SchUseStrongCrypto/SystemDefaultTlsVersions registry keys for older frameworks. Make sure TLS 1.2 is enabled in Windows.

Common causes

  • .NET Framework < 4.7 defaulting to TLS 1.0
  • SecurityProtocol not set
  • SchUseStrongCrypto registry missing
  • TLS 1.2 disabled in Schannel
  • Legacy Windows Server 2008/2012

⚡ Quick fix

  1. Set ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls12
  2. Upgrade the target framework to 4.7+/.NET
  3. Enable SchUseStrongCrypto in the registry

Detailed fix by platform

C#

  1. ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls12;

How to diagnose

  1. Framework — Below 4.7?
  2. SecurityProtocol — Set?
  3. Registry — Strong crypto?

🔧 Still not fixed?

Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:

Where this error sits

Origin: Network. Errors that are often confused with or caused by this one (click to open):

0x800CCC0D — Outlook error 0x800CCC0D: Cannot find the server — the host name of the mail server couldn't be resolved (Email / SMTP)0x800CCC0DCould not establish trust relationship for the SSL/TLS secure channel — .NET: System.Net.WebException: The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel (SSL / TLS)Could not establish t…CRYPT_E_NO_REVOCATION_CHECK — curl (Windows Schannel): schannel: next InitializeSecurityContext failed: CRYPT_E_NO_REVOCATION_CHECK (0x80092012) - The revocation function was unable to check revocation for the certificate (SSL / TLS)CRYPT_E_NO_REVOCATION…Django — Django send_mail: ssl.SSLError: [SSL: WRONG_VERSION_NUMBER] (EMAIL_USE_SSL vs EMAIL_USE_TLS on the wrong port) (Email / SMTP)Djangoopenssl.cnf — OpenSSL: Can't open openssl.cnf for reading / error loading config file (SSL / TLS)openssl.cnfPFX export — Cannot export or import the certificate with its private key (PFX/PKCS#12 has no private key) (SSL / TLS)PFX exportSchannel — curl: (35) schannel: next InitializeSecurityContext failed (SEC_E_UNTRUSTED_ROOT / SEC_E_ALGORITHM_MISMATCH) (SSL / TLS)SchannelSchannel 36874 — Schannel Event 36874: An TLS connection request was received from a remote client application, but none of the cipher suites supported by the client application are supported by the server (SSL / TLS)Schannel 36874.NET TLS

Explore the map of this error Full error map →

🧠 Still stuck? Analyze your error

Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.

💬 What worked for others

No tips yet — did something else fix this for you?

Share what worked for you

Tips are checked by an editor before they appear. Links are removed.