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 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.

Plugins that interact with comments

Some plugins can cause issues with Jetpack Comments. Examples include Antispam Bee, Spam Free WordPress, Bad Behavior, and CommentLuv. More information on troubleshooting issues with Jetpack Comments.

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 Stats and cause stats to stop being collected. To fix it, disable the Jetpack integration. Go to Complianz → Integrations → Plugins and disable the slider next to Jetpack.

LiteSpeed Cache

Last tested on June 29, 2023, with version 5.5

The LiteSpeed Cache plugin can affect Jetpack Stats. To fix it, disable the Localize Resources feature. Go to LiteSpeed Cache → Page Optimization → Localization and disable the Localize Resources feature.

LiteSpeed Cache and Jetpack Boost

Last tested on July 10, 2025

The LiteSpeed Cache plugin can conflict with Jetpack Boost’s Critical CSS and caching features. This may result in layout issues after updating Jetpack Boost or enabling its Optimize CSS Loading feature.

The following workarounds can help resolve the conflict:

• In Jetpack → Boost, disable Optimize CSS Loading to check if the issue resolves.
• In LiteSpeed Cache, go to Page Optimization → CSS Settings, and disable Load CSS Asynchronously.
• Avoid enabling overlapping optimizations (for example, do not use both plugins to combine or defer CSS).
• If needed, test by disabling one plugin at a time to identify the source of the conflict.

We recommend using only one plugin to handle CSS optimization or page caching, not both at once.

See Troubleshooting Critical CSS in Jetpack Boost: potential conflicts with other performance plugins.

Beaver Builder: Jetpack Gallery Widget and VideoPress

Last updated on January 22, 2026

Beaver Builder has a known incompatibility with the Jetpack Gallery Widget. Additionally, the frontend media uploader does not work with VideoPress. Beaver Builder has details here.

AMP

Last updated on July 15, 2026

When the AMP plugin is installed, it triggers an error message after a Jetpack Form is submitted:

Even though the server responded OK, it is possible the submission was not processed.
Please contact the developer of this form processor to improve this message.

To remove the message, configure any pages or posts using Jetpack Forms to bypass AMP. You can do this in the editor by toggling Enable AMP off.

Jetpack VaultPress Backup

Restoring a backup may cause duplicate charges for automated subscription renewals

If your site uses a plugin that manages automated billing — such as WooCommerce Subscriptions or other membership or subscription plugins — restoring a site backup with Jetpack VaultPress Backup may cause customers to be charged again for a subscription period they have already paid.

This happens because the restore reverts the database to the point in time the backup was taken. Any subscription renewals that were successfully processed after that snapshot are erased from the restored database, causing the billing plugin to treat them as unpaid and re-charge customers. This affects any plugin that uses Action Scheduler or post meta to track scheduled billing, not only WooCommerce Subscriptions.

Before restoring a backup on a site with active automatic subscription renewals, we strongly recommend that you take the following steps:

• Notify customers of the planned maintenance window.
• Pause all automatic renewals before restoring.
• Review and manually cancel any duplicate orders immediately after the restore.

The Jetpack VaultPress Backup team is working on adding a pre-restore warning when subscription plugins are detected.

Hosting

Cloudflare’s Rocket Loader

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

Flywheel

Last tested on June 26, 2025

Flywheel hosting disables access to xmlrpc.php by default. This will prevent Jetpack from connecting properly. You can reach out to their support team to ask them to enable access to xmlrpc.php for your site. Once that is done, you should be able to connect Jetpack.

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 has instructions for changing this setting.

Pantheon

Last updated on June 18, 2025

Jetpack connection and XML-RPC

By default, Pantheon blocks access to xmlrpc.php, which is required for Jetpack to connect to your site. To allow Jetpack to connect, follow Pantheon’s documentation to enable access to xmlrpc.php.

Jetpack VaultPress Backup and Jetpack Scan

Jetpack VaultPress Backup and Jetpack Scan do not work on Pantheon due to its restrictions on file system access. These features rely on direct file access, which Pantheon’s infrastructure does not support.

WP Engine

Jetpack connection and XML-RPC

Last updated on July 25, 2026

XML-RPC access (required by Jetpack) is blocked by default on WP Engine environments created after April 2022. You will need to adjust WP Engine’s Web Rules to allow access. They have instructions on their site and you can reach out to their support team for assistance. You can restrict access to Jetpack IPs if you wish.

Jetpack VaultPress Backup

Last updated on July 25, 2026

In order to use Jetpack VaultPress Backup on WP Engine, you need to add server credentials. We have instructions on how to add credentials to Jetpack. You will need to obtain your credentials directly from WP Engine.

Custom CSS

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 recommend switching to another host — you can see hosts running promotions 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 not possible.

Vodafone blocking Jetpack image CDN

There are known issues with Vodafone UK blocking some Jetpack image URLs (for example, 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.

How to address these messages

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

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.

Miscellaneous

Fatal error when you try to access Jetpack Forms in your WP Admin

If you encounter an error message about an undefined get_browser_display_name method:

Uncaught Error: Call to undefined method AutomatticJetpackDevice_DetectionUser_Agent_Info::get_browser_display_name()

You likely have an outdated version of the WP Super Cache plugin. Please make sure to update to version 3.0.3 or higher.

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.