How Do I Add My License Keys and Add-Ons to LifterLMS On My Website?
To locate your License Key for any LifterLMS product:
- Log in to your account at LifterLMS.com/my-account.
- Navigate to the “Active Licenses” area.
- Locate the long string of characters under your license (e.g., l1M5-asdfasdfasdf…).
- Copy this key to your clipboard.

To find the area to enter your license key, head to LifterLMS > Add-ons & More in your WordPress dashboard.

Once you click the ‘My License Keys‘ button, a dropdown will appear where you can remove any existing license keys or enter your new license key. If you’re entering a new license key, copy and paste your key, then select ‘Add New‘.

Once your key is added, you’ll be able to install any add-ons right from the backend of your website, on the same screen under LifterLMS > Add-ons & More. You’ll also have access to any updates the LifterLMS development team releases.
Once you have your key, add it to your WordPress site to receive automatic updates and support.
- Log in to your WordPress site as an administrator.
- Navigate to LifterLMS > Add-ons & More.
- Click on the My License Keys button. A dropdown menu will appear.
- Paste your license key into the field.
- Click Add New.




The number of active websites you can use your license key on depends on your plan. Please review the LifterLMS pricing page for current details, but generally:
- Single Add-on & Earth Bundle: 1 Active Site
- Universe Bundle: 5 Active Sites
- Infinity Bundle: Unlimited Active Sites
Staging and development sites (copies of your website used strictly for testing) do not count against your active site limit, provided they meet the criteria below.
LifterLMS uses an automated system to detect staging environments based strictly on the site’s URL. To ensure your staging site does not count against your active license limit, your site’s URL must match one of our system-approved staging patterns.
If your staging site URL does not match these patterns, it will be counted as a “Live” site and will use a seat on your license.
Approved Subdomains
A site is considered “staging” if the URL begins with any of the following terms:
- dev. (e.g., dev.example.com)
- develop. (e.g., develop.example.com)
- local. (e.g., local.example.com)
- stage. (e.g., stage.example.com)
- staging. (e.g., staging.example.com)
- test. (e.g., test.example.com)
- testing. (e.g., testing.example.com)
Approved Hosting Environments
Your site is automatically considered “staging” regardless of the subdomain if the URL is hosted on one of these specific platforms:
- RunCloud (.temp-site.link)
- WP Engine (.wpengine.)
- Kinsta (.kinsta.)
- Flywheel (.flywheelsites.)
- Cloudways (.cloudwaysapps.)
- Pantheon (.pantheonsite.)
- GoDaddy Managed WP (.myftpupload.)
- GridPane / Access Domain (.accessdomain.)
- Sandboxes: .poopy.life, .wpsandbox.pro
Note: RunCloud staging sites use .temp-site.link, so they count as staging automatically.
If you see an error message stating that your license limit has been reached, check the URL of your staging site.
If you are using a custom subdomain to test a new design (such as new-design.example.com or v2.example.com), this will not be recognized as a staging site. To fix this without upgrading your license, you must rename your subdomain to one of the approved terms listed above (e.g., rename new-design.example.com to staging.example.com).
Some hosting providers use caching or security measures that may prevent the license key from being saved correctly. If you are unable to save your key, you can add the following code snippet to your site (in your child theme’s functions.php file or using a code snippets plugin) to resolve this:
add_filter( 'llms_use_server_for_environment_fetch', '__return_true' );
If you see the message “Whoa! Something went wrong there! Please refresh the page and retry” when saving your LifterLMS settings, it can feel like something has broken, but in most cases, it hasn’t.
This error is usually caused by a security check failing behind the scenes, not a problem with your courses, settings, or data. Your site and data are still intact, and the issue can be resolved with a small adjustment.
This guide walks you through a simple fix so you can get back to saving your settings and continuing your work without disruption.
Why This Error Happens
This happens when the LifterLMS security system can’t verify the request sent to the server. Developers call this a “nonce verification” failure.
While this looks like a plugin conflict, it’s usually caused by how your hosting server communicates with WordPress. It often looks like a plugin conflict, but the cause is usually how your hosting server communicates with WordPress. This is common on certain hosting providers such as GoDaddy.
To fix this, you’ll need to tell LifterLMS to use a different method to identify your server environment. You can do this by adding a small PHP code snippet to your site.
How to Fix the Error Using a Code Snippet
Follow these steps to apply the fix to your WordPress site.
- Install a code snippets plugin if you don’t already have one. You can learn more about this in our guide on how to add custom code to LifterLMS.
- Navigate to the snippets section in your WordPress dashboard. If you’re using the Code Snippets plugin, go to Code Snippets > + Add Snippet.
- Choose the “Add Your Custom Code (New Snippet)” option and click the Use snippet button.
- Set the “Code Type” to “PHP Snippet” using the dropdown menu.
- Copy and paste the following code into the “Code Preview” box:
add_filter( ‘llms_use_server_for_environment_fetch’, ‘__return_true’ );
- Give your snippet a title, such as “Fix LifterLMS Settings Save Error.”
- Toggle the switch to Active and click the Save Snippet button.
- Go back to your LifterLMS settings and try to click Save Changes again.
Need Further Help?
If you encounter this same error when trying to save your LifterLMS license key, the process is the same. You can find more details about this specific scenario in our documentation on adding your license key to LifterLMS.
If you still see the error after adding the snippet, make sure it’s active. If the problem continues, contact the LifterLMS support team for further assistance.


