Need help?

Our experts have had an average response time of 13.52 minutes in October 2021 to fix urgent issues.

We will keep your servers stable, secure, and fast at all times for one fixed price.

CloudFlare error 525 SSL handshake failed – How to fix

by | Nov 12, 2021

Wondering how to resolve CloudFlare error 525 SSL handshake failed? We can help you.

As part of our Server Management Services, we assist our customers with several CloudFlare queries.

Today, let us see how our Support techs resolve this error.

How to resolve CloudFlare error 525 SSL handshake failed ?

Typical, error looks as shown below:

Error 525: SSL handshake failed

Error indicates that the SSL handshake between Cloudflare and the origin web server fail.

This only occurs when the domain is using Cloudflare Full or Full (Strict) SSL mode.

This is cause by a configuration issue in the origin web server.

Today, let us see the steps followed by our Support techs to resolve it:

1. Firstly, make sure you have a valid SSL certificate install on your origin server.

To display your origin certificate, replace 203.0.113.34 with the origin IP address of your web server & replace www.example.com with your domain and host name:

$ curl -svo /dev/null https://www.example.com --connect-to ::203.0.113.34 2>&1 | egrep -v "^{.*$|^}.*$|^* http.*$"

2. Then, check with your hosting provider to make sure they’re listening on port 443/whatever other port 106 you are using.

3. Next, check to make sure your origin server is properly configure for SNI 1.9k.

4. The cipher suites 469 that Cloudflare accepts 477 and the cipher suites that the origin server supports do not match.

Review the cipher suites your server is using to ensure they match what is supported by Cloudflare.

5. Next, if you are the site owner and you’re only seeing errors intermittently, this suggests the TCP connection between Cloudflare and your origin is being reset during the SSL handshake causing the error.

Then, ask your hosting provider/system administrator to check if there are any server issues.

7. Note that Apache must configure 404 to log mod_ssl errors and nginx includes these errors in its standard error log, but it may  necessary to increase the log level.

8. Next, pause 203 Cloudflare or update your local hosts file to point directly at your server IP to test that your server is presenting a SSL certificate.

If you do not have a certificate install on your server you can generate one using our Origin CA 450 certificates.

9. If you cURL to the origin on port 443 and receive the error error:1408F10B:SSL routines:ssl3_get_record:wrong version number.

Disable TLS 1.3 on the Edge Certificates tab of the SSL/TLS app on the Cloudflare dashboard.

Then, to determine what TLS version is currently supported, use the following cURL command.

Then, replace MYORIGINIP with the IP address shown on the A record of your DNS app in the Cloudflare dashboard and www.example.com with your domain:

$ curl -svo /dev/null https://www.example.com --connect-to ::MYORIGINIP 2>&1 | egrep -v "^{.*$|^}.*$|^* http.*$"

10. Finally, test a specific TLS version by adding one of the following options to your cURL:

–tlsv1.0
–tlsv1.1
–tlsv1.2
–tlsv1.3

[Stuck in between? We’d be glad to assist you]

Conclusion

In short, today we saw steps followed by our Support Techs to resolve CloudFlare error 525 SSL handshake failed.

PREVENT YOUR SERVER FROM CRASHING!

Never again lose customers to poor server speed! Let us help you.

Our server experts will monitor & maintain your server 24/7 so that it remains lightning fast and secure.

GET STARTED

0 Comments

Submit a Comment

Your email address will not be published. Required fields are marked *

Privacy Preference Center

Necessary

Necessary cookies help make a website usable by enabling basic functions like page navigation and access to secure areas of the website. The website cannot function properly without these cookies.

PHPSESSID - Preserves user session state across page requests.

gdpr[consent_types] - Used to store user consents.

gdpr[allowed_cookies] - Used to store user allowed cookies.

PHPSESSID, gdpr[consent_types], gdpr[allowed_cookies]
PHPSESSID
WHMCSpKDlPzh2chML

Statistics

Statistic cookies help website owners to understand how visitors interact with websites by collecting and reporting information anonymously.

_ga - Preserves user session state across page requests.

_gat - Used by Google Analytics to throttle request rate

_gid - Registers a unique ID that is used to generate statistical data on how you use the website.

smartlookCookie - Used to collect user device and location information of the site visitors to improve the websites User Experience.

_ga, _gat, _gid
_ga, _gat, _gid
smartlookCookie

Marketing

Marketing cookies are used to track visitors across websites. The intention is to display ads that are relevant and engaging for the individual user and thereby more valuable for publishers and third party advertisers.

IDE - Used by Google DoubleClick to register and report the website user's actions after viewing or clicking one of the advertiser's ads with the purpose of measuring the efficacy of an ad and to present targeted ads to the user.

test_cookie - Used to check if the user's browser supports cookies.

1P_JAR - Google cookie. These cookies are used to collect website statistics and track conversion rates.

NID - Registers a unique ID that identifies a returning user's device. The ID is used for serving ads that are most relevant to the user.

DV - Google ad personalisation

IDE, test_cookie, 1P_JAR, NID, DV, NID
IDE, test_cookie
1P_JAR, NID, DV
NID
hblid

Security

These are essential site cookies, used by the google reCAPTCHA. These cookies use an unique identifier to verify if a visitor is human or a bot.

SID, APISID, HSID, NID, PREF
SID, APISID, HSID, NID, PREF