License Activation Notices
In rare cases, you will not receive an error or notice in your WordPress admin dashboard. Please review your server’s error log with your webhost support team or server admin to locate the error message.
If you want to know how to activate your plugin, please go to the plugins page and click on its Installation Guide.
Common activation notices
You’ve reached your activation limit. You must upgrade your license to use it on this site.
You’re trying to activate a license that already has hit it’s maximum number of activations.
Be sure you haven’t switched to a different domain recently.
You can either deactivate the license on one of the activated websites by going to SEO -> Extensions -> Licenses and pressing Deactivate.
Or you can upgrade your license to a higher plan.
Warning! You’re blocking external requests which means you won’t be able to get [plugin] updates.
WP_HTTP_BLOCK_EXTERNAL in your wp-config.php file without adding the right domain(s) to
You can either remove
WP_HTTP_BLOCK_EXTERNAL from your wp-config.php file or add my.yoast.com to
WP_ACCESSIBLE_HOSTS in your wp-config.php file.
This is a comma separated list, so you can have: api.wordpress.org,my.yoast.com and it should work. It would then look something like this:
define( 'WP_ACCESSIBLE_HOSTS', 'api.wordpress.org,my.yoast.com' );
Did you know you can upgrade your license?
You’ve almost hit your maximum activations for your license.
If you want to use the license on more sites than originally purchased, you can always upgrade your license to a higher limit.
Your license is expiring in X days, would you like to extend it?
Your license will expire in X days. You will no longer receive updates and support after it expired.
If you want to continue receiving updates and support, please extend your license. The plugin can always be used without a license.
Your license has expired. You must extend your license in order to use it again.
Your license has expired.
If you want to receive updates and support, please extend your license. The plugin can always be used without a license.
Failed to activate your license, your license key seems to be invalid.
The license key you entered is invalid.
You can request your license key at the License Support page by entering your email address in the box ‘License retrieval’. You will receive an email with your license key.Please copy and paste it in the license key box, to prevent typo’s. Still not working? Please try the suggestions here to fix the invalid error message.
Request error: Couldn’t connect to host.
Your server is unable to connect to my.yoast.com.
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.
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.
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”
The server couldn’t connect to my.yoast.com with cURL.
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: php_network_getaddresses: getaddrinfo failed: Name or service not known.
The error indicates a DNS issue where something in the server configuration fails to translate the URL to an IP.
Since this is a server-issue, we cannot fix this for you, your webhost will have to fix this. Learn more about this error here.
Request error: “XYZ”
Your server responded to the request with error “XYZ”.
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.