Dan (a11n)

Hi Rolf

The user agent used by Jetpack Monitor is?jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com). In the LiteSpeed Cache settings, you should add the entire user agent string to the “Exclude from cache by User Agent” section. This means including?jetmon/1.0 (Jetpack Site Uptime Monitor by WordPress.com)?in your LiteSpeed Cache exclusion settings, not just?jetmon/1.0. This will help ensure that caching recognizes the specific Monitor agent and does not serve cached content in response to its checks.

Thank you!

Hi there

I tested with the 404 plugin you mentioned, but I was unable to reproduce the error. I created a page and set it as the 404 page in Settings > Reading, then I viewed the 404 page directly and was redirected to the home page, but I didn’t get any critical CSS errors.

Could you provide more detailed steps that we can take to try and reproduce this error?

Hi there

If you’re still experiencing this issue, could you please post your site URL here so that we can have a look?

If you want it to remain private, you can also contact us via this contact form.

If you choose to reach out directly, please include a link to this thread.

Thanks!

Hi there,

I understand that you’re experiencing issues with Jetpack not recording search terms, even though traffic is being recorded. This can happen for several reasons, such as search engines not passing on the search term data, privacy/cookie settings, or a potential misconfiguration.

As explained here, if we don’t know the search terms, we display them as “Unknown search terms.” Certain search engines do not disclose search terms due to privacy concerns. It seems that may be the case on your site, as I do see searches being recorded, but with unknown search terms.

Hi there. This was a temporary issue, which was since resolved. Thanks for letting us know.

Hi again

In order to help troubleshoot this issue, could you please contact support directly via the WooCommerce app’s Help section (Settings > Help and Support > Contact Support)? This will send the app logs to the Woo support team so they can investigate and help figure out what is happening.

Thanks.

Hi there,

The error messages you’ve provided indicate that there might be an issue with the Jetpack sync process. This kind of “Commands out of sync” error can happen if previous database commands were not properly closed before new commands were issued.

Conflicting Plugin: Since you mentioned you had an issue with a third-party plugin, it would be beneficial to first ensure that there are no conflicts between that plugin and Jetpack. You can do this by temporarily deactivating other plugins and seeing if the problem persists.

If that doesn’t help, could you please provide your website URL so that I can have a closer look at the issue? Additionally, if there have been any more recent error logs or other symptoms of the problem, please share those details as well.

Thank you!

Hi there

When I try to visit your site I see “Website Temporarily Unavailable” – so I guess you turned back on the coming soon page?

We don’t have any records of a connection for the url you provided, so we’ll need some more information to help further.

Could you contact us via this contact form and mention this thread?

Thanks

Hi there

Thanks for bringing this to our attention. I see that you are in touch with the plugin author now via the other thread, and they are working on getting this fixed, so I’ll mark this one resolved to keep the conversation in one place.

Thanks!

Your site’s xmlrpc.php file is showing a blank page instead of the required message, which is preventing Jetpack from connecting.

This is most likely because a plugin, theme, or your site’s wp-config.php file has extra “blank spaces” (new lines, spaces, tabs, …) before the first <?php in the file.

I’d recommend following the troubleshooting steps listed here to fix that:

https://jetpack.com/support/getting-started-with-jetpack/what-do-these-error-messages-mean/blank-lines-xmlrpc/#troubleshooting

Let us know how that goes!

Hi there

Thanks for the extra details. I checked your site and your Jetpack connection is actually working fine. You can confirm that by entering your site URL here:

https://jptools.wordpress.com/debug/

From the screenshot you shared, it seems the issue here is instead an invalid response from your site when trying to log into your admin account.

I will check with our WooCommerce colleagues about this and get back to you. Thanks for your patience.

Hi there

This is the expected behaviour for a multisite network, it will only show the cached pages of the site you’re on, not the whole network. You would need to go into the settings in each site to view the cached pages of each site in the network.

Hi there,

Thank you for providing the details about the issue you’re encountering with Jetpack Boost’s “defer non-essential javascript” feature and your website’s behavior, particularly concerning the loading of no_photo.gif.

From your description, it seems that the ImgError function, which should handle the case when an image fails to load, is not available at the time it’s needed because the script containing this function is being deferred.

One possible workaround would be to exclude that specific script from being deferred. For details of how to do that, please see our FAQ, specifically the section about How do I exclude some JavaScript files from being deferred?

Please try excluding that script and test if the issue with the image loading persists.

If you require further assistance or if this workaround does not resolve your issue, please reply in this thread with the outcomes and any additional details you can provide.

Hi there. I see that you’ve been in touch with WordPress.com support regarding this issue, so I’ll mark this one as resolved. Since you have a paid WordPress.com plan, it’s best to continue to contact WordPress.com support directly if you need further help.

Hi there,

The issue you’re describing with the Jetpack comments form seems intermittent and it’s possible that there could be a conflict with another plugin or script on your site. Since you’ve already tried clearing your browser’s cache, the next step would be to troubleshoot for potential conflicts.

Here are some steps you can take to identify the issue:

1. Check for Plugin Conflicts: Deactivate all other plugins except for Jetpack, and see if the issue persists. If the form works correctly, then reactivate your plugins one by one until you recreate the issue. This will help pinpoint the conflicting plugin.
2. Check your Theme:?Temporarily switch to a default WordPress theme like Twenty Twenty-One to see if the issue might be with your current theme.
3. Browser Extension Conflict: Test the page in an incognito window or different browsers to rule out any browser extension conflicts.
4. Server-Side Caching: Check with your hosting provider if there are any server-side caching configurations that could be interfering with the form’s functionality.
5. Content Delivery Network (CDN):?If you are using a CDN like Cloudflare, try disabling it temporarily or check for any specific rules that might be causing the issue.

If none of these steps resolve your issue, could you verify if the issue is happening on specific posts or pages, or if it seems to be completely random across your site?