Fixing the "Invalid CSRF Token" Error
"Invalid CSRF Token" means the server refused a form because the security code sent with it did not match your session. The cause is almost always the connection or the hosting setup, not your data.
When the Message Appears
You see it right after submitting a form, most often on the admin sign-in page. WISECP 3.x shows the message with a link to this article. WISECP 5.x asks you to refresh the page and try again.
In WISECP 5.x, a page opened over a plain http:// address shows a different message: signing in requires a secure (HTTPS) connection.
Why It Happens
Every form carries a one-time security code tied to your browser session. The server rejects the form when that code is missing or no longer matches.
Tasks
Fix the Error
- Open the page with its
https://address and refresh it. - Wait until the page has fully loaded, then fill in the form and send it again.
- If your site is behind Cloudflare, turn off Rocket Loader under Speed › Optimization, or disable it for the admin folder with a rule. Then purge the Cloudflare cache.
- If every attempt still fails, ask your hosting provider to check that PHP can write session files.
The form is then accepted and you are signed in.
Things to Watch
The server stops before it runs the action, so there is nothing to repair afterwards. Send the form again once the cause is fixed.
Related Articles
Merci pour votre retour !
L'équipe d'assistance est disponible 24h/24 pour tout ce que vous ne trouvez pas dans la base de connaissances.