Back to Community
Home / Community / Plugin → Jetpack

Fixing the 'Invalid/missing blog nonce' Error in Jetpack Social

35 threads Sep 16, 2025 Plugin → Jetpack

Content

Many users encounter the frustrating "Invalid/missing blog nonce. All core actions require a valid nonce" error when trying to connect their social media accounts through Jetpack Social. This guide explains what this error means and provides the most effective solutions to resolve it.

What is a Nonce and Why Does This Error Occur?

A "nonce" is a security token used in WordPress to protect URLs and forms from certain types of misuse. The error indicates that this security check is failing when Jetpack Social attempts to connect to a platform like Facebook, Instagram, or LinkedIn. Based on community reports, this is often caused by a temporary glitch in the Jetpack connection, a conflict with security plugins, or caching issues.

Common Solutions to Fix the Nonce Error

If you see this error, try the following troubleshooting steps, starting with the simplest first.

1. Refresh Your Connection

The most common and successful fix is to refresh the connection between your site and the Jetpack service.

  • Log out and back in: Completely log out of your WordPress admin dashboard and then log back in. This can refresh your session and generate a new, valid nonce.
  • Disconnect and reconnect Jetpack: Go to the Jetpack settings in your WordPress dashboard, disconnect the plugin, and then reconnect it to WordPress.com. This often resolves underlying connection issues that cause the nonce error.
  • Try in a new browser tab: After reconnecting, open the Jetpack Social connection page in a completely new browser tab and try adding the social connection again.

2. Check for Plugin and Hosting Conflicts

Security plugins, caching plugins, or server-level security settings can sometimes block the requests necessary for Jetpack to function.

  • Temporarily disable other plugins: Deactivate any security, caching, or firewall plugins (e.g., Shield Security, Disable XML-RPC) temporarily. Then, attempt the social connection again. If it works, you know one of those plugins was the cause. Reactivate them one by one to identify the culprit and adjust its settings to allow Jetpack.
  • Check XML-RPC: Jetpack requires XML-RPC to be enabled and accessible. Verify that it is not being blocked by a plugin or your hosting provider. You can test this by visiting yoursite.com/xmlrpc.php. It should show a message like "XML-RPC server accepts POST requests only," not a "Not Found" or "Forbidden" error.
  • Contact your host: If you are unsure, contact your hosting provider and ask them to ensure that XML-RPC is not blocked and that Jetpack's IP addresses are not being filtered by their firewall.

3. Clear Browser and Site Cache

A stale browser cache can sometimes interfere with the process.

  • Clear your browser's cache and cookies, or try using a private/incognito browser window to make the connection.
  • If you use a caching plugin or service (like Cloudflare), clear all its caches as well.

4. Check the Social Platform Itself

For LinkedIn specifically, check if Jetpack needs to be re-authorized on their platform.

  • Log into your LinkedIn profile, go to Settings & Privacy > Data Privacy > Permitted services.
  • If "Jetpack" is listed there, remove it.
  • Return to your WordPress dashboard and try initiating the connection from Jetpack Social again.

What If the Problem Persists?

If you have tried all the steps above and the error continues, it may be due to a known issue that the Jetpack development team is actively working on. Several users in the community have reported that the issue was resolved on the service side after a fix was deployed. In these cases, simply trying to reconnect your social accounts a day or two later was successful.

When seeking help online, be prepared to provide details such as the URL of your site and the exact steps you took before the error appeared. This information is crucial for others to provide accurate assistance.

Related Support Threads Support