Known issues

Some plugins, themes, or hosting features are known to conflict with Jetpack’s functionality. Until these conflicts are resolved, you can find some workarounds and guidance on this page.

If Jetpack is not working as expected, a good idea first troubleshooting step is to check for a plugin conflict or a theme conflict. If you find a compatibility conflict with a theme or another plugin, please reach out to their development team to see if they can fix the issue.

Plugins known to conflict with Jetpack

Plugins that disable access to XML-RPC

Jetpack depends on the XML-RPC connection in WordPress. Plugins that restrict access to xmlrpc.php will cause issues with Jetpack. You will either need to configure these plugins to allow access to xmlrpc.php or add Jetpack’s IPs to the plugin’s allowlist. Learn more about Jetpack’s usage of XML-RPC.

Plugins that minify and combine JavaScript

Plugins that minify and/or combine JavaScript files can conflict with Jetpack’s functionality. If you are having an unexpected issue with Jetpack, we recommend that you disable this functionality and test the feature. If that resolves the problem, you will know that the issue is with the modification. 

Plugins that add “Coming Soon” or “Maintenance Mode” Functionality

Some plugins that add a “coming soon” or “maintenance mode” message to WordPress may prevent Jetpack from communicating with your site. If you are having trouble with a broken Jetpack connection, please disable any “Maintenance Mode” or “Coming Soon” plugins and try again. Depending on the plugin, it may also be possible to configure them in a way that doesn’t block the Jetpack connection. Please consult the plugin’s documentation and/or developers for assistance.

Plugins that Restrict Access to the REST API

Plugins that require authentication to access the REST API can cause the Jetpack Connection to break. To fix this, you can either turn off the plugin or configure it so that the /jetpack/v4/ and /wpcom/v2/ namespaces are on an allow list.

Plugins that Manage the Ads.txt File

If you use WordAds on your site, you need to remove plugins that manage your site’s Ads.txt file. Instead, you can use Jetpack to manage your Ads.txt file.

Complianz – GDPR/CCPA Cookie Consent 

Last tested on August 31, 2022, with version 6.3.1

The Complianz – GDPR/CCPA Cookie Consent plugin can affect Jetpack’s Stats feature and cause stats to stop being collected. To fix it, the Jetpack integration must be disabled. To disable Complianz’ integration with Jetpack, navigate to “Complianz > Integrations > Plugins” and disable the slider next to Jetpack. 

LiteSpeed Cache

Last tested on June 29, 2023, with version 5.5

LiteSpeed Cache plugin can affect Jetpack’s Stats feature. To fix it, the Localize Resources feature must be disabled. To disable Localize Resources in LiteSpeed Cache, navigate to “LiteSpeed Cache > Page Optimization > Localization” and disable the Localize Resources feature.

---

Hosting

Cloudflare’s Rocket Loader

Cloudflare’s Rocket Loader is currently not compatible with Jetpack Likes, Site Stats, some shortcodes, and other Jetpack features using JavaScript. You’ll consequently need to disable this feature in your Cloudflare settings.

Custom CSS and WP Engine

Custom CSS will not be applied to visits by search engine bots on WP Engine sites due to a rule on their server to prevent bots from loading dynamic content. This can impact users, for example, whose Custom CSS modifies the layout to meet Google’s mobile-friendly designation.

We highly recommend switching to another host – you can see hosts running promotions here.

GoDaddy

Last tested on June 29, 2023

Some sites hosted by GoDaddy can display a “Hi Jetpack! All Systems go.” message on the site’s landing page when Jetpack’s Downtime Monitor is enabled. If you see this message on your site, change your site’s Sucuri Caching settings to “Site Headers” instead of the recommended setting. Sucuri have instructions for changing this setting here.

Staging Sites on SiteGround

Due to the way that SiteGround handles URLs on their staging sites, connecting Jetpack on a SiteGround staging site is impossible.

Vodafone Blocking Jetpack Image CDN

There are known issues with Vodafone UK blocking some Jetpack image URLs (e.g., those beginning with https://i0.wp.com, https://i1.wp.com, or https://i2.wp.com), which prevents images from displaying on Jetpack sites. If you use a Vodafone broadband network and find some missing images, we suggest first connecting to a different network to see if the images are displayed. If you are affected by this issue, please contact Vodafone directly for assistance.

Windows Cache Extension for PHP

We have some reports that this extension for Windows IIS servers can prevent Jetpack from connecting correctly to WordPress.com. If your site is on an IIS server, please try to disable this extension if you are having difficulty connecting Jetpack to WordPress.com.

---

Notices and Deprecation Warnings

On rare occasions, Jetpack updates or releases may trigger PHP notices or deprecation warnings. These messages usually do not affect site functionality, but may appear on the front-end or in debug logs when WordPress debugging is enabled.

Jetpack 14.4

Released on March 4, 2025

Message:

Notice: Function register_rest_route was called incorrectly. REST API routes must be registered on the rest_api_init action. Instead route 'site/update-historically-active-modules' with namespace 'my-jetpack/v1' was not registered on this action.

Details: A REST API route was registered in the wrong place. While the API itself still works, this message may appear in debug mode.

Resolution: Update to Jetpack 14.4.1 or later, where this issue is fixed. If you cannot update right away, you can temporarily hide the message.

Jetpack 14.3

Released on February 4, 2025

Message:

Deprecated: Class Jetpack_Geo_Location is deprecated since version 14.3 with no alternative available. in ... wp-includes/functions.php

Details: This occurs when themes or plugins use the now-deprecated Jetpack_Geo_Location class removed in Jetpack 14.3. It does not break functionality, but may be triggered by third-party code.

How to address these messages

If you do not want these notices displayed publicly on your site:

1. Open your wp-config.php file using FTP or your hosting file manager.
2. Add the following line above the line that says /* That's all, stop editing! Happy blogging. */:
   • define( 'WP_DEBUG_DISPLAY', false );
3. Save and close the file.

This will suppress the display of notices on the site while still logging them (if logging is enabled). For additional guidance, see Debugging in WordPress.

Misc.

Contact Info Widget Adds Invalid Structured Data to Address

Jetpack’s deprecated Contact Info Widget can add invalid Schema.org Structured Data to addresses, which causes the address to fail validation. To resolve this issue, we recommend using a free plugin such as Schema & Structured Data for WP & AMP to add all required fields correctly.

Social Media Icons Not Appearing in Comments Widgets

Check the permissions of the third-party cookie. When denied, social media icons may not appear. You can read more about that on the Troubleshooting Jetpack Comments page.

Country Blocks and Internet Restrictions

As part of our commitment to freedom of speech, you can find options for bypassing country-specific internet restrictions in our documentation on WordPress.com. While the methods in this documentation are generally legal, always exercise caution when deciding to use them, and research the situation in the country you are connecting from first. You can also find our Country Block List Transparency Report here.