Title: Jetpack Comments
Last modified: December 9, 2022

---

# Jetpack Comments

 *  Resolved [Kev Provance](https://wordpress.org/support/users/kprovance/)
 * (@kprovance)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/jetpack-comments-8/)
 * I’ve enabled the Jetpack option “Let visitors use a WordPress.com, Twitter, Facebook,
   or Google account to comment.”
 * The comments form loads up. But when I make a comment using my admin account 
   and click Submit, the only thing that happens is the comment box is filled with
   the actual page, like the page loaded within the window, and no comment was saved.
 * I checked the FAQ, and no ‘know issue’ plugins are loaded.
 * The page I need help with: _[[log in](https://login.wordpress.org/?redirect_to=https%3A%2F%2Fwordpress.org%2Fsupport%2Ftopic%2Fjetpack-comments-8%2F%3Foutput_format%3Dmd&locale=en_US)
   to see the link]_

Viewing 3 replies - 1 through 3 (of 3 total)

 *  Thread Starter [Kev Provance](https://wordpress.org/support/users/kprovance/)
 * (@kprovance)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/jetpack-comments-8/#post-16276741)
 * Update: I ran the theme (one I wrote…I do this professionally) and also tried
   it against the twenty-twenty-two theme on another install and received the “nonce
   verification failed.’ message, which I see has been an ongoing issue.
 * Fortunately, I have PHP debugging experience. The reason this happens is that
   the nonce generated at page load is not the same nonce that Jetpack checks again
   upon submission.
 * Upon further digging, the nonce is different because wp_get_current_user fails
   upon submission, and returns 0 as the user_id when it is typically something 
   else at page load (in my case, 2).
 * I’m not sure why the wp_get_current_user fails upon submission. Hopefully, the
   developers can figure it out. For posterity, I checked this not only with my 
   theme but also twenty-twenty-two. Both produced the same error for the same reasons.
 *  Thread Starter [Kev Provance](https://wordpress.org/support/users/kprovance/)
 * (@kprovance)
 * [3 years, 4 months ago](https://wordpress.org/support/topic/jetpack-comments-8/#post-16277739)
 * Okay, I discovered the problem. It’s a conflict with the WPBruiser plugin ([https://wordpress.org/plugins/goodbye-captcha/](https://wordpress.org/plugins/goodbye-captcha/)).
   It looks as if that plugin has been abandoned.
 * To make the two work together, one will have to disable the “Protect Comments
   Form” in the WPBruiser > WordPress options.
 * FYI for anyone experiencing this issue.
 *  [Bruce (a11n)](https://wordpress.org/support/users/bruceallen/)
 * (@bruceallen)
 * Happiness Engineer
 * [3 years, 4 months ago](https://wordpress.org/support/topic/jetpack-comments-8/#post-16282789)
 * Hi [@kprovance](https://wordpress.org/support/users/kprovance/)
 * Thank you for the updates on this issue!

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Jetpack Comments’ is closed to new replies.

 * ![](https://ps.w.org/jetpack/assets/icon.svg?rev=2819237)
 * [Jetpack - WP Security, Backup, Speed, & Growth](https://wordpress.org/plugins/jetpack/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/jetpack/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/jetpack/)
 * [Active Topics](https://wordpress.org/support/plugin/jetpack/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/jetpack/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/jetpack/reviews/)

## Tags

 * [Jetpack comments](https://wordpress.org/support/topic-tag/jetpack-comments/)

 * 3 replies
 * 2 participants
 * Last reply from: [Bruce (a11n)](https://wordpress.org/support/users/bruceallen/)
 * Last activity: [3 years, 4 months ago](https://wordpress.org/support/topic/jetpack-comments-8/#post-16282789)
 * Status: resolved