The "Form Was Unable to Submit" Error
Visitors fill out your contact form, press send, and get "The form was unable to submit. Please contact the site administrator to resolve this issue." — the message from a working form that the server rejected.
Common signs of this issue
- Visitors see "The form was unable to submit. Please contact the site administrator to resolve this issue." after pressing send.
- The form itself looks normal — fields, labels, and the submit button all display and accept typing.
- You stop receiving form messages, but usually only find out when someone phones or emails to say "your form doesn't work."
- The error appears either instantly on clicking submit, or after a short pause with a spinner.
- It may affect every visitor, or only some — often people on certain networks, or people whose messages contain links.
- It often starts after a plugin update, a new security or caching plugin, a captcha change, or the host tightening its firewall.
Safe checks you can do yourself
None of these require sharing passwords with anyone.
- Submit the form yourself the way a stranger would: logged out, in a private/incognito window. A test while logged in can pass while every real visitor fails, because owners bypass caching and some security checks.
- Try again from your phone on mobile data (Wi-Fi off). If it works there but not from your office network, the block is between certain networks and your site, not in the form itself.
- Notice the timing. An instant rejection usually means a firewall or security rule refused the submission outright. A pause first usually means the data was sent and a server-side check — captcha, security token, or spam filter — failed it.
- If the form uses a captcha (the "I'm not a robot" box, or invisible checking), confirm in the form plugin's settings that the site key and secret key are still filled in and match the same captcha service — expired or mismatched keys quietly fail every submission.
- Clear your site's cache, and if your caching plugin allows it, exclude the contact page from caching. Cached pages can hand visitors a stale security token, and the form rejects anything submitted with an old one.
- Check the form plugin's own screens: most keep an entries list or an error log. If entries are arriving but no email reaches you, that is a different problem — email delivery — with its own guide.
- Before contacting anyone, note the exact conditions that fail — which page, which device, logged in or out, message with or without links. That list is most of the diagnosis.
What this usually means
This exact wording is what popular WordPress form plugins show when the submission reached the server and the server said no. The form's front end is fine — the rejection happens behind the scenes, after your visitor presses send — so the fix is almost never in the form's fields or design. It is in whatever is screening submissions.
The usual suspects, roughly in order: a security plugin or the host's firewall (often a system called ModSecurity) deciding the submission looks suspicious; broken or expired captcha keys failing every human; a caching plugin serving a stale security token — called a nonce, a one-time pass proving the submission came from a fresh copy of the page; or another plugin's JavaScript conflicting with the form's and garbling what gets sent.
There is an awkward truth in the message itself: it tells the visitor to contact the site administrator — through a website whose contact form is the thing that is broken. Most visitors will not hunt for your phone number; they simply leave. That is why this error runs undetected for weeks, and why testing your own form on a schedule is worth the two minutes it takes.
What not to do
- Don't assume the form is fine because it works for you while logged in — logged-in owners often skip the very checks that are failing for visitors.
- Don't delete and rebuild the form. The form is usually not the broken part, and the rebuilt one will hit the same server-side block.
- Don't turn off your security plugin or firewall entirely just to make the form work — adjust the one rule involved instead, or have someone do it for you.
- Don't remove the captcha as a quick fix without a plan — spam floods in within days, and real messages can end up filtered into the trash.
- Don't change several plugins at once while testing. Change one thing, test the form, write down the result.
- Don't forget the visitors who already failed — once the form works, check your entries list and spam folder, and consider whether recent quiet weeks were really quiet.
When to get help
This error sits at the junction of several systems — the form plugin, a security layer, caching, sometimes the host's firewall — and the fix is usually one precise change: adjusting a single firewall rule, refreshing a pair of captcha keys, or excluding one page from cache. Someone who works with WordPress forms regularly can usually pinpoint which layer is rejecting submissions in under an hour, because the server's logs say so plainly, while trial and error can leave the form dead for days. A dead contact form is invisible lost business — every failed inquiry is a customer who was ready to talk to you — so if your logged-out test still fails after the captcha and cache checks, handing over your notes on exactly when and how it fails is the fastest, cheapest path back to a working form.
Not sure what to do next?
Answer a few short questions and we'll point you to the safest next step — DIY, a freelancer, or a direct review. No passwords required.
Is this a business website? If this issue may be costing you leads, sales, or trust, you may want a direct review instead of trial and error.
Frequently asked questions
What does "The form was unable to submit, please contact the site administrator" mean?
It is the standard message some WordPress form plugins, including WPForms, show when the server rejected the submission. The visitor's part worked; a behind-the-scenes check — a firewall, a captcha, a security token, or a spam rule — refused to accept the data.
Why does my form work for me but not for visitors?
You are probably testing while logged in. Logged-in administrators often bypass caching and some security checks. Always test logged out, in a private browsing window, and ideally from a phone on mobile data as well.
Can a caching plugin really break my contact form?
Yes. Forms include a short-lived security token proving the page is fresh. If a cached copy of the page is served for hours or days, visitors submit with an expired token and are rejected. Excluding the contact page from caching usually fixes it.
Is this error caused by reCAPTCHA?
Often. If the captcha's site key or secret key is wrong, expired, or belongs to a different captcha type than the form expects, every submission fails validation even for real humans. Reconnecting the keys in the form plugin's settings is a common one-step fix.
How do I stop this happening again without noticing?
Test your own form on a schedule — monthly at least, logged out, from a device you don't normally use. Some form plugins and monitoring services can also alert you when submissions stop arriving for an unusually long stretch.