WordPress: Are you sure you want to do this? Please try again. (nonce check failed)
A WordPress security nonce didn’t validate — the page was open too long, cached, or a plugin/theme form is broken.
Seen on:
WordPress
Meaning
Nonces expire after 12–24 hours and are tied to the user session. Cached admin pages, logging in again in another tab, or plugin bugs (missing nonce field) trigger it.
Common causes
- Page left open past nonce lifetime
- Admin/frontend page cached with an old nonce
- Logged in/out in another tab
- Plugin/theme form missing the nonce
⚡ Quick fix
- Reload the page and try again
- Exclude admin and logged-in pages from caching
- Update/deactivate the plugin causing it
Detailed fix by platform
WordPress
- php
// In a form wp_nonce_field('save_settings', '_mynonce'); // When processing check_admin_referer('save_settings', '_mynonce');
How to diagnose
- Timing — How long was the page open?
- Cache — Page cached?
- Plugin — Which action triggers it?
🔧 Still not fixed?
Many errors look alike. If the steps above didn’t solve it, one of these is probably what you’re facing:
Similar errors
- 403 Forbidden wp-admin WordPress: 403 Forbidden on wp-admin, wp-login.php or admin-ajax.php
- An automated WordPress update has failed An automated WordPress update has failed to complete - please attempt the update again now
- Another update is currently in progress WordPress: Another update is currently in progress.
Most viewed in WordPress
Other ways to find it
🧠 Still stuck? Analyze your error
Paste the full message, response headers or stack trace — we'll detect the platform and point to the most likely cause.
Was this page helpful?
Report a correction or suggest an improvement
Last updated 7 Oct 2026