Skip Navigation

[Resolved] TLS error on Toolset activation key

This thread is resolved. Here is a description of the problem and solution.

Problem: Registration error "cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been received"

Solution: Update your server to use TLS v1.1 or manually update the plugins instead of automatic updates.

This support ticket is created 6 years, 8 months ago. There's a good chance that you are reading advice that it now obsolete.

This is the technical support forum for Toolset - a suite of plugins for developing WordPress sites without writing PHP.

Everyone can read this forum, but only Toolset clients can post in it. Toolset support works 6 days per week, 19 hours per day.

Sun Mon Tue Wed Thu Fri Sat
8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 8:00 – 12:00 - -
13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 13:00 – 17:00 - -

Supporter timezone: America/New_York (GMT-04:00)

Tagged: 

This topic contains 6 replies, has 2 voices.

Last updated by Christian Cox 6 years, 7 months ago.

Assisted by: Christian Cox.

Author
Posts
#706175
Screenshot 2018-04-21 at 11.40.55 AM.png

I am trying to:
Enter the license key that my Toolset account generated for my site.

Link to a page where the issue can be seen:
See image below

I expected to see:
The site get registered to the key.

Instead, I got:
Error: "cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been received."

Deleted all associated sites in the Toolset license section with no luck.

How do I get the license/account I paid for registered?

#710599

Hi, please go to wp-admin > Settings > General and check the two URLs at the top. They should both point to "https" URLs. Then temporarily deactivate all plugins, clear your browser cache and cookies, and try to register once more. Let me know if this does not resolve the issue for you.

#765480

Hi this is still not working after trying the steps above. Still getting:

cURL error 35: gnutls_handshake() failed: A TLS fatal alert has been received.

#769560

Okay thanks, the next thing I can try is to log in to your site, unregister your site key, and try to register the site again with my master key. If that works, then we can assume there is a problem with your key. If not, then it's most likely a server configuration issue. If you approve, please provide login credentials in the private reply fields here.

#858048

Okay it does not appear to be a problem with the key, it appears to be a problem with the server environment. For security, our system requires cUrl using at least TLS 1.1. Please ask your host provider to upgrade the hosting server to a PHP cUrl version that has TLS v1.1.

#870846

My hosting provider has confirmed they are using curl 7.22 and have no plans on upgrading at this time.

Was the requirement for TLS 1.1 a recent change to the Toolset suite? I do not recall having this issue when I started using the plugins a couple months back (?).

#873030

Yes, it's recent. We made some changes to the automatic updater for security purposes. If your host isn't planning to update, you can continue using the Toolset plugins, but it will be required to manually deactivate, delete, and then update plugins in the Toolset suite.