Troubleshoot Jetpack Scan

Last updated:

Did Jetpack Scan stop working? Did you get an email that said Jetpack is having trouble scanning your site? Follow these troubleshooting steps to fix issues with Jetpack Scan.

Jetpack Scan checks these files for security threats:

  • All files in the plugins, mu-plugins, themes, and uploads directories.
  • Select files from your WordPress root directory, like wp-config.php.
  • Other select files inside the wp-content directory.

Once a scan completes, you will receive a notification if any threats are found. These notifications will be in WP Admin, via email, and on your WordPress.com dashboard.

There are a few things that can prevent Jetpack from scanning your site. If you are concerned that Jetpack Scan is not working, please follow the steps below.

Check the Jetpack connection

A working Jetpack connection is required to get Jetpack Scan working properly.

  1. Check your site’s connection on the Jetpack Debug (jptools.wordpress.com/debug) page.
  2. Troubleshoot the connection using the Fixing Jetpack Connection Issues guide.

Add server credentials

Auto-fixes over HTTP require the Jetpack Protect plugin v4.2 or higher.

If your site’s Jetpack connection is working and Jetpack Scan is still having problems scanning the website, the next step is to add server credentials.

Server credentials are also required to auto-fix any threats if an HTTP-based fix fails or isn’t supported by your setup.

To add server credentials:

  1. Follow our Adding Credentials to Jetpack guide.
  2. On a self-hosted site with Jetpack 16.4 or later, you can also go to Jetpack → Protect → Settings and click “Add server credentials” (or “Manage server credentials“) in the Scan card. Your site’s settings in Jetpack Cloud open in a new tab.
  3. Unsure what server credentials are? Check out our documentation about SSH, SFTP, FTPS, and FTP Credentials.

If your last scan didn’t complete

On a self-hosted site with Jetpack 16.4 or later, a failed scan shows up on the Scan results card at Jetpack → Protect as “Your last scan didn’t complete“, with the line “We can’t confirm your site is free of threats until a scan finishes.” Work through the steps on this page, then start a new scan with “Scan site“.

Check file permissions

  1. To help Jetpack scan your site successfully, ensure your SFTP/SSH/FTP credentials have full read and write file permissions to your WordPress installation directory.
  2. Wait for a new scan to run the next day, or start one now. On a self-hosted site with Jetpack 16.4 or later, go to Jetpack → Protect in WP Admin and click “Scan site” at the top of the page. You can also start one from the Scan page in Jetpack Cloud.

Review security and firewall settings

Web Application Firewalls (WAF) such as Cloudflare or Sucuri can prevent Jetpack Scan from working, or a security plugin installed on the site may be blocking certain network requests.

  1. If you are comfortable, please review your WAF or security plugin settings and allow requests from Jetpack’s IP addresses.
  2. If not, we recommend temporarily disabling these services/features while troubleshooting Jetpack Scan. Generally, this can be achieved by disabling the plugin, but you might also have to disable a feature in the service provider’s dashboard (i.e.: pausing Cloudflare from their dashboard).

Speak to Your Host

If the above troubleshooting has not worked to get Jetpack Scan running, you may need to speak to your webhost.

  1. If you are not sure about who your site is hosted with you can check using WordPress.com site-profiler.
  2. Ask your host to allowlist Jetpack IP addresses.
  3. Ask your host to check for any other blocks between them and Jetpack.

If a scan is taking several hours, or if a scan seems to be stuck, that may be something the Jetpack team needs to look into. Please contact us directly and let us know.

Reporting False Positives

A plugin or theme that Jetpack Scan still flags after you update it may have a WPScan advisory that lists the vulnerability as unfixed. In that case, the plugin or theme developer is the one to contact, as explained in Understanding the version number in a threat alert. For any other alert you think is a mistake, contact us and we’ll check it for you.

Still need help?

Please contact support. We’re happy to advise.

Was this article helpful?