LifterLMS Fatal Error or White Screen? How to Fix It Safely
A calm, step-by-step way to recover a LifterLMS site from a white screen or “critical error”: get back in with recovery mode or WP-CLI, read the…
Read articleA LifterLMS checkout error costs you a sale and usually a support email. The student sees a red message, or worse, nothing at all: they click the purchase button, the page reloads, and they are back where they started.
This guide is for course owners and developers who need to fix that quickly. It explains the error messages LifterLMS shows at checkout and what causes each one, the silent failures that show no message, where to find the gateway's own explanation for a declined payment, and what to do with orders left as Pending or Failed.
If you are still setting up your checkout, read our LifterLMS checkout setup guide first. This article assumes a checkout that used to work, or should work, and does not.
A LifterLMS purchase passes through three stages, and the fix depends on which one failed:
Check the order list first. Go to LifterLMS > Orders and look for an order from the student at the time of the attempt. No order at all points to stage 1. An order with the status Pending Payment or Failed points to stage 2. An order with a successful transaction but no enrollment points to stage 3, which we cover in when a student cannot access a course.
These are the validation messages built into LifterLMS core, quoted as they appear.
| Message | What it means | Fix |
|---|---|---|
| This access plan is not available. | The plan is unpublished, or set to members only and the buyer is not a member | Check the plan's Plan Availability and the product's status |
| This product is not available for purchase. | The course has a restriction in effect, such as a closed enrollment period or full capacity | Check Enable Enrollment Period and Enable Course Capacity on the course |
| Invalid Access Plan ID. | The checkout link points to a plan that no longer exists | Rebuild the button or link from the current plan |
| Coupon code "…" not found. | The code does not match any coupon | Check spelling and that the coupon is published |
| This coupon has reached its usage limit… / This coupon expired on… | Coupon limits or expiry | Edit the coupon's limits or dates |
| This coupon cannot be used to purchase "…". | The coupon is restricted to other products or plans | Add the product to the coupon's allowed list |
| No payment method selected. | The plan costs money but no gateway was chosen, often because none is enabled | Enable a gateway under LifterLMS > Settings > Checkout |
| The selected payment gateway does not support recurring payments. | A subscription plan combined with a gateway, usually a third-party one, that only handles one-time payments | Use a gateway that supports recurring billing, or change the plan's frequency |
| You must agree to the … to continue. | A Terms and Conditions Page is set and the box was not ticked | Nothing to fix, unless your theme hides the checkbox |
| There was an error creating your order, please try again. | The order post could not be created | Check the PHP error log; usually a database or fatal error |
| Suspicious activity detected. Try again in a few minutes. | Spam protection has blocked the visitor's IP | See the spam protection section below |
| CAPTCHA validation failed — please try again. | reCAPTCHA or Turnstile rejected the request | Check keys and score threshold |
If a student reports a message that is not in this list, it almost certainly came from the payment gateway or from an add-on, and the gateway section below applies.
This is the most confusing failure, and it has a specific cause. Every LifterLMS checkout form contains a security nonce. When the form is submitted, LifterLMS verifies it before doing anything else. If the nonce is missing or invalid, LifterLMS simply ignores the submission. No error is shown and the page loads again.
A nonce becomes invalid in a few predictable ways:
JavaScript errors are the other cause of a "dead" purchase button. Gateways such as Stripe collect card details through JavaScript. If an optimisation plugin delays or combines those scripts, or another plugin throws an error first, the button does nothing. Check the browser console on the checkout page. Testing with other plugins disabled on a staging copy confirms the cause.
LifterLMS has built-in protection against card-testing attacks, where bots hammer a checkout with stolen card numbers. It lives under LifterLMS > Settings > Security:
Leave spam protection on. Card-testing attacks can cost you gateway fees and get your merchant account reviewed. Do watch for false positives, though:
When validation passes and the payment still fails, the explanation lives with the gateway. Three places tell you what happened.
Open the order in LifterLMS > Orders. The notes panel records status changes, transactions and, for many gateways, the reason a charge failed.
Each payment gateway's settings include a Debug Log option ("Enable debug logging"). Turn it on, reproduce the problem with a test purchase, then read the log under LifterLMS > Status > Logs. The LifterLMS Stripe documentation describes the same process for Stripe, where the log file name begins with "stripe-". Turn logging off again when you are done.
Stripe and PayPal record every attempt, including ones that never reached your site. A decline code such as insufficient funds or a failed authentication is a matter between the buyer and their bank. Your job is to make sure the message reaches the buyer clearly and that they can try again.
LifterLMS uses these order statuses: Pending Payment, Active, Completed, On Hold, Pending Cancellation, Cancelled, Expired, Refunded and Failed.
If money was taken but the order still shows Pending Payment, do not simply enroll the student and move on. Find out why the confirmation did not arrive, which is usually a webhook problem, because it will keep happening to other buyers.
"There was an error creating your order" and blank checkout pages usually mean PHP is failing. On a staging copy, or briefly on production during a quiet period, enable logging in wp-config.php without displaying errors to buyers:
define( 'WP_DEBUG', true );
define( 'WP_DEBUG_LOG', true );
define( 'WP_DEBUG_DISPLAY', false );
Reproduce the checkout, then read wp-content/debug.log. The file and line number in the error tell you which plugin is responsible.
Almost always because the form's security nonce failed, usually due to page caching of the checkout. Exclude the checkout page from all caches and test in a private window.
Check the order notes, then the gateway's dashboard. For more detail, enable the gateway's Debug Log setting and read the log under LifterLMS > Status > Logs.
The block is temporary and clears after the failure window. Ask them to wait and try again with one card. If it happens regularly to genuine buyers, check that your server sees real visitor IP addresses.
Yes. Use your gateway's test mode on a staging site, or a 100% coupon for a quick enrollment test, and place a full purchase as a logged-out visitor in a private window.
Work through the stages in order: check whether an order exists, read the exact message, rule out caching, then read the gateway log. Most checkout problems are solved by a cache exclusion, a gateway setting or a webhook fix.
If you are losing sales and cannot find the cause, or the fix involves custom gateway code, our LifterLMS support team can investigate on a staging copy of your site. Contact us with the error message and an order number.
A calm, step-by-step way to recover a LifterLMS site from a white screen or “critical error”: get back in with recovery mode or WP-CLI, read the…
Read article
A step-by-step method for tracking down the plugin, theme or custom code that is breaking LifterLMS, using staging, Health Check troubleshooting…
Read article
Configure page caching, CDNs and script optimisation for LifterLMS so pages stay fast while logged-in learners, quizzes, lesson timers and checkout…
Read articleSkip the trial and error. Get specialist LifterLMS help and ship faster.