License Activation Notices

Last update: 14 September, 2017

A license key is no longer needed to use our premium plugins because we launched a customer portal where you can find and manage all the Yoast SEO products you own. If you don’t have an account yet or want to know how it all works, this guide will get you started.

If the current version of the plugin (from version 5.2 and onwards) asks for a license key, please enter a 0 for the license key to force the plugin to switch to our new customer portal.

Subscription Connection Errors

Table of Contents

Request error: Couldn’t connect to host.

Cause
Your server is unable to connect to my.yoast.com.

Solution
There are several possible causes, but all of them should be fixed by your webhost. For example by adding an exception to the firewall rules or updating the cURL module to the latest version. We cannot fix this for you, your webhost will. Or you
can switch to another webhost.

Request error: Connection timed out.

Cause
Your server was unable to communicate to my.yoast.com within the set time limit. This can be caused by, for example, a very slow webhost or a firewall.

Solution
Since this is a server-issue, we cannot fix this for you, your webhost will have to fix this. Or you can switch to another webhost.

Request error: “400 Bad Request”

Cause
The server couldn’t connect to my.yoast.com with cURL.

Solution
Test if cURL can connect to https://my.yoast.com. In rare cases, your server’s IP may be blocked by our firewall. Please contact our support team with your server IP, the failed cURL output and a traceroute showing the fail occurs on our side. Your webhost can provide you with the IP, cURL output and traceroute as they must be completed from your server NOT your computer.

Request error: “XYZ”

Cause
Your server responded to the request with error “XYZ”.

Solution
Search our Knowledge Base for the specific error. If not found, please send the complete error to the support desk of your webhost. They should be able to help you fix this, since this is a server-issue. Or you can switch to another webhost.

Was this article helpful? ·