jetpack 11.4 is broken in WP 6.0.3

Hi @paul,

Can 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. Please include a link to this thread if you choose to reach out directly.

Thanks.

https://paulbeard.org/wordpress/

Just to update the thread…I have restarted everything from the web server and all its processes, the network gateway/wireless router, my laptop. It’s still not working. I guess I can live without it but WordPress makes a strong case for the value of Jetpack so I’d rather not.

I have had the same problem this morning:
You have version 11.3.2 installed. Update to 11.4. View version 11.4 details.
Compatibility with WordPress 6.0.3: 100%
This crashed the site so I disabled it and reinstalled V11.3.2
All good again.

Jetpack need to look into this.

Thanks, @paul, for sharing your site URL and that update.

I’ve just debugged the Jetpack connection for https://www.paulbeard.org/wordpress/, and there seems to be a problem with the XML-RPC file. You can confirm this using this Jetpack debug tool.

You can try what the debug tool recommends, which is to run the following command in the terminal:

curl -A 'Jetpack by WordPress.com' -d '<methodCall><methodName>demo.sayHello</methodName></methodCall>' https://www.paulbeard.org/wordpress/xmlrpc.php

Your host appears to be blocking attempts to access that file because the attempts are being interpreted as XMLRPC attacks. Please reach out to the host about this. If necessary, ask them to add Jetpack’s IP range to the allowlist. The IPs can be found at https://jetpack.com/support/hosting-faq/.

Regards.

Thanks, @kbsmayo, for sharing your report.

We’d be happy to look into this if you can share more information. Could you share the PHP error notice/message you get when you update Jetpack and your site crashes?

You can get that information by adding the following code to your site’s wp-config.php file:

define('WP_DEBUG', true);

if ( WP_DEBUG ) {
?
????????@error_reporting( E_ALL );
????????@ini_set( 'log_errors', true );
????????@ini_set( 'log_errors_max_len', '0' );
?
????????define( 'WP_DEBUG_LOG', true );
????????define('WP_DEBUG_DISPLAY', false);
????????define( 'CONCATENATE_SCRIPTS', false );
????????define( 'SAVEQUERIES', true );
?
}

Once you’ve done that, update Jetpack again, and after the crash, check the?wp-content/debug.log?file for error messages.

Please look for the most recent log messages, especially any that reference Jetpack files and send that info to us here, and then replace the following:

define('WP_DEBUG', true);

with this:

define('WP_DEBUG', false);

in your wp-config.php file.

Thanks.

This all started when I saw that jetpack was not connected…it kept failing to connect, even though I was logged into www.ads-software.com. Reinstalling it brought on the inability to display the wp-admin CSS so I have to delete it to do anything in there.

I just tried he debug steps recommended above and the xmlrpc.php file downloads were a couple of days ago it used to display with some message I have forgotten.

I have a feeling I am going to have to tear out wordpress root and branch to get to the bottom of this and I’m not even sure that will work. I suspect there is some lingering cruft in the database that is hosing things up. How do I remove all traces of jetpack from there just to be sure?

Also, I added the code block above to create a debug log and none appeared after a few page loads. Not sure I see where the log file is defined unless it’s in the core somewhere.

How can I get jetpack 11.3.x so I can see if it makes any difference?

Thanks @ihenetudan
I did that and as it happens the update went through without any issue.
It may have been just a temporary glitch this morning or perhaps a conflict with one of the other plugins that need updating also.

Nonetheless, all is working fine with V11.4 for me now.
Thanks.

I think this is bigger than jetpack…my javascript console is full of 404 errors that make no sense. The files are where they are referenced. No plugins are loaded. Site health check never completes loading its status.

I think something has gone very wrong here but I don’t see any recent medication dates on files and wp-cli sees no checksum issues. nginx and pgh-fpm config files haven’t changed, based on their modification times.

Kind of at a loss here…I just downloaded and installed a frech copy of WP 6.0.3 and I still see the same issues. The actual site is fine but anything to do with wp-admin spews a ton of errors to the console, I can’t load plugins, the site health screen never finishes loading. I wonder if there is something in the database from the repeated install/remove cycles that has gotten messed up. wp_options had 73 lines that contain “jet” in option_name (308 rows total). Why would the wp-admin pages be so messed up while the site pages are fine?

UPDATE: I have installed a fresh 6.0.2, same issues. I have tested a new install of 6.0.3 in the latest versions of Chrome and Firefox as well as Safari. Same issues recur.

The errors, to recap:
wp-admin’s site health page never finishes loading
adding the jetpack plugin causes all the CSS for wp-admin to be ignored
many javascript errors about jQuery or 404 error for files that are accessible.

Anything else I can try? Kind of annoyed to have just purchased mpl-publisher and between the time I paid for it and trying to use it, these issues are making it inoperable, as well as all the other issues noted.

• This reply was modified 2 years, 4 months ago by paul.

I was able to recover by exporting to a WXR file and importing into a new wordpress instance. Not ideal but it works. One of the benefits of self-hosting is that you get full control but you’re also in full control.

Not gonna install jetpack and friends just yet. Once bitten, twice shy…

• This reply was modified 2 years, 4 months ago by paul.

Hi @paul –

I’m glad that you were able to get your site working.

It looks like Jetpack isn’t properly connected per:

https://jptools.wordpress.com/debug/?url=https%3A%2F%2Fpaulbeard.org%2Fwordpress%2F

Could you try reinstalling Jetpack and reactivating to cycle the connection?

Not any time soon, after all this. Jetpack was the reason everything went pear-shaped, as described above. Not in a hurry to gamble on a repeat of that.

Okay, since we’re no longer going to be troubleshooting the connection I’ll mark this thread as resolved.