"Invalid security token" fault when posting comment but not using anti spam bee

Can you replicate the problem using the default Twenty Fourteen theme with all other plugins deactivated?

Thanks, before trying that I have more information which might help?

I just re activated the Jetpack plugin and posted a few test comments which posted fine. Then I copied and pasted the same comment that caused the Invalid security token error and got the exact same problem.

So there’s a strong implication that it was choking on something in this specific comment.

I had used a little html markup including 2 text links and a blockquote section, as well as a word encased in

So by taking out one at a time I was able to discover the specific thing that seems to have caused the error and it was this bit

they 

I use the   because emphasis markup always slants the word so much that it joins up with the next word so I force and extra space. When I removed the   the comment posted OK.

Can anyone make any sense of this?

Ironically my use of the offending code hasn’t stopped me commenting in here ??

Your site and these forums are completely independent of one another.

I seriously doubt that Jetpack is causing this problem but it could be a server security configuration issue. See: https://www.ads-software.com/support/topic/cant-save-a-post-or-page-with-certain-text

I tried to leave a comment on your site, and received the following error message:
https://i.wpne.ws/Taub

As you can see, the problem appears to be caused by the Stop Spammer Registrations Plugin.

Since you already use Akismet, you probably don’t need Stop Spammer Registrations, or WP-SpamFree. Akismet already goes through each one of your comments and filters out spam.
If you don’t want Spammers to register on your site, you can turn off registrations in Settings > General in your dashboard.

I hope this helps.

Thanks very much. I only recently installed these extra plugins after experiencing a mass of spam registrations, about one every hour, which they totally stopped. No one ever posted anything (presumably because of Akisment) but Akismet didn’t stop the constant registrations and I couldn’t stop the email notifications for them.

I’ve disabled them, the last thing I want is for people to waste time composing a comment and for it to be blocked. I’ve noticed almost all comments have stopped but put it down to poor traffic – though I would have expected at least one angry email if people were being stopped from commenting.

In my case it seemed to definitely be the   which caused the Invalid security token which when I disabled Jetpack was fixed.

I’ve just realised that the code I keep refering to isn’t showing up for yo – Doh! I need to enter it in the code tags.

The markup which appeared to cause the Invalid security token error was
  which I had inserted after a word surrounded with <em></em>

So when I had entered “<em>they</em>&nbsp; it caused the error but when I removed just the   it posted the comment OK.

However, when I disabled Jetpack, I could post the original code OK

Has anyone got an idea why using the code ? in a comment would cause the Invalid security token error? Which is exactly what happened in my case.

I’m afraid I wasn’t able to reproduce on my end. I can use <em>they</em>&nbsp; in comments on my test site without creating any issues.

Do you still experience the issue when all other comment and anti spam plugins are deactivated? If so, can you please use Jetpack’s Debugger module to send us some more information about your site?

1) Go to the Jetpack page in your dashboard.
2) Click on the Debug link appearing at the bottom of the page.
3) Click the link that says “click here to contact Jetpack support.”
4) Fill in the description box and your name and email address.
5) Click the “Contact Support” button.

Thanks!

Thank you for your reply. It might have to go down as one of those bizarre unexplained incidents.As it happens I’ve disabled comments section of jet pack anyway because I wanted to remove the website field from comments, which jet pack won’t allow. The plug-in that I used to remove the field only works with the standard comments form.

The issue is in Jetpack conflicting with Antispam Bee, ok, now, I don’t want to disable Jetpack plugin as I like the share facility it offers and I don’t want to disable Antispam Bee as the amount of spam I get by not having Antispam Bee is simple don’t worth the hassle.

If this is the same scenario you have in your WordPress based blog, with the same plugins and experiencing the same issue here is the work around.

The solution to solve the error invalid security token in WordPress comments is simple by disable the Jetckpack Comments in Jetpack settings. Really simple.

More details here:

The solution to solve the error invalid security token in WordPress comments is simple by disable the Jetckpack Comments in Jetpack settings. Really simple.

I agree with rogeruk. I have the same problem, and I solved it by disabling Jetpack Comments.