You will want to ensure your license is active for two reasons:
- To receive automatic updates for the plugin in your WordPress dashboard. This includes new features, bug fixes, and compatibility improvements we release. Many of the features we add come directly from user feedback.
- To get technical support from our team when you need it.
Below are a few common reasons why your license key might not be activating properly.
- Your License Key Has Expired
- Your License Key Is Already In Use
- Security Plugin Is Blocking Activation
- .htaccess File Blocking Activation
- Coming Soon or Maintenance Mode Plugin Blocking Activation
- Outdated cURL Version or Host Blocking Requests
- SSL Error
- 403 Forbidden Error
Your License Key Has Expired
Your license key automatically renews every year until canceled. We send out multiple email reminders to let you know. However, there is a number of reasons why this might not work, such as:
- You have canceled your automatic payment profile
- Your credit card has expired
- You close or changed PayPal accounts
You can renew an expired license key using either of these methods:
- From your Account page. Log into your Account, click on “View License”, and click on the “Renew Now” link.
- From the Checkout. Find the plugin and click the Purchase button. On the Checkout, you will see a “Click to renew an existing license” link. Click here, paste your expired (or soon-to-expire) license key, and click “Apply License Renewal.” You can then complete the purchase to renew your existing license key.
Your License Key Is Already In Use
The number of sites you can activate your license key on depends on the license you purchased.
- 1 Site – Personal
- 3 Sites – Business
- Unlimited Sites (no limit)
You can install and activate the Perfmatters plugin on your local development or staging environment without impacting your activation count. Learn more.
If you need to activate the plugin on more sites than your current license key permits, you can upgrade at any time from your account.
Security Plugin Is Blocking Activation
Some WordPress security plugins may block connections to our licensing server (API requests), which would prevent you from activating your license key. An easy way to test this is to temporarily disable the security plugin and try activating your license again.
According to EDD, the iThemes Security plugin is known to have a setting that can cause this issue. The setting is called “Filter Suspicious Query Strings in the URL.”
To resolve the issue, simply disable the “Filter Suspicious Query Strings in the URL” setting. If you are not using iThemes Security, it will be named something different, though similar.
.htaccess File Blocking Activation
Some WordPress sites have special rules configured in a
.htaccess file on the server to add additional protection. However, this means it might also be blocking our licensing server (API request). You can try removing the special rules and activating your license key again. If you are unsure if you have something configured or not, your hosting provider might be able to help.
Coming Soon or Maintenance Mode Plugin Blocking Activation
Coming Soon and Maintenance Mode WordPress plugins sometimes block all external requests. This means it might prevent you from activating your license key. An easy way to test this is to temporarily disable the plugin and try activating your license again.
Outdated cURL Version or Host Blocking Requests
cURL is used for transferring data with URLs. Your WordPress site uses cURL to reach out to our licensing server for activation. If you are having problems activating, it could be due to an outdated PHP cURL extension on your web host. Or it could be they are blocking outgoing connections.
Here’s a copy-and-paste message you can send your hosting provider for them to check:
I’m currently installing a WordPress plugin on my site which uses the PHP cURL extension. Can you please confirm the following?
– The PHP cURL extension is installed and updated to at least version 7.68
– HTTP requests to https://perfmatters.io are not blocked
We run the latest versions of OpenSSL on our servers. If your hosting provider is using an older version of OpenSSL, it could generate an SSL handshake error such as SSL23_GET_SERVER_HELLO. You should ask your hosting provider to update OpenSSL to the latest version.
403 Forbidden Error
If you get a 403 forbidden error, this means there is another type of problem on your WordPress site preventing it from communicating with our licensing server. Check out Kinsta’s article on how to fix a 403 forbidden error.
Still Can’t Activate?
If none of the troubleshooting steps above helped, please open up a support ticket.