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+.
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 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
- Set
ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls12 - Upgrade the target framework to 4.7+/.NET
- Enable SchUseStrongCrypto in the registry
Detailed fix by platform
C#
ServicePointManager.SecurityProtocol |= SecurityProtocolType.Tls12;
How to diagnose
- Framework — Below 4.7?
- SecurityProtocol — Set?
- 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:
Similar errors
- 0x800CCC0D Outlook error 0x800CCC0D: Cannot find the server — the host name of the mail server couldn't be resolved
- Could 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
- 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
Most viewed in SSL / TLS
- HTTPSConnectionPool: Max retries exceeded (SSLError) Python requests: HTTPSConnectionPool(host='api.example.com', port=443): Max retries exceeded with url: /v1 (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] ...')))
- DST Root CA X3 expired (old clients fail) Old clients: certificate has expired — Let's Encrypt chain uses expired DST Root CA X3 (OpenSSL 1.0.x, Android < 7.1.1)
- Keystore was tampered with, or password was incorrect Java keytool: java.io.IOException: Keystore was tampered with, or password was incorrect
Other ways to find it
Where this error sits
Origin: Network. Errors that are often confused with or caused by this one (click to open):
🧠 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.
Report a correction or suggest an improvement
Last updated 18 Nov 2026