WordPress: “The request was aborted: Could not create SSL/TLS” Error Handling
In the Low-Profile Activity Report -> https://secure.cardcom.solutions/ReportsNew/LPDReport.aspx
Go to Developer Information - the Transaction Response Details tab.
If the following error message is received through WordPress: The request was aborted: Could not create SSL/TLS
Send these instructions to the website hosting company for resolution:
To enable us to connect to your servers, the following Cipher Suites must be enabled:
TLS_DHE_RSA_WITH_AES_256_GCM_SHA384 (0x9f) Forward Secrecy | 256 |
TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 (0x9e) Forward Secrecy | 128 |
TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384 (0xc02c) Forward Secrecy | 256 |
TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 (0xc02b) Forward Secrecy | 128 |
For all errors of the following type: Server sent fatal alert: protocol_version
The standard for TLS 1.3 must be supported.
Forward this guide to the business’s website hosting company so they can upgrade the TLS version to a current version.
The following website checks SSL certificates:
https://www.ssllabs.com/ssltest
Upgrade the servers to the TLS 1.2 standard.
Upgrade the end user to the TLS 1.3 standard.
This also applies to Cloudflare, where applicable.
After completing the process, you may see that there is an issue with IE11. Make sure this issue does not occur by adding the Cipher Suites listed above.
You can click IE11 to view the list of Cipher Suites that must be enabled (the ones listed above).