Problems after update Jetpack
-
Updated the Jetpack, got whitescreen.
Reinstalled Jetpack, get this messege:
The Jetpack server was unable to communicate with your site https://www.andrefahlstrom.se [HTTP 403]. Ask your web host if they allow connections from WordPress.com. If you need further assistance, contact Jetpack Support: https://jetpack.com/support/Jetpack run fine before update.
-
Same on my two sites.
Wordpress and all other plugins are current.In browsing other entries, I’d suggest looking at “Updated Plugin and Site is Down (Fatal Error)”. It may resolve your issue. I’m going to try it also.
Well, as was stated in one of the replies to the above mentioned post, it now works!
I fixed it by accessing the site via FTP and disabling the JetPack plugin by renaming the plug-in folder. Then I logged into the WP Admin page, deleted the plug-in and reinstalled it fresh. It seems to be fine now.
I have tested to reinstall jetpack several times now, but same problem appears every time.
It seems that JetPack 4.8 requires PHP 7, otherwise it causes blank-screen errors (even in debug mode). JetPack 4.8 calls random_int(), which is available in PHP 7 and up. Ref: https://swinginthinkin.com/wordpress/wordpress-jetpack-fatal-error/
Automattic team – you are not seriously requiring PHP 7 are you? That’s a pretty bold thing to do without, I don’t know, telling anyone that you were doing that? Your plugin has become an essential part of WordPress. Would be nice if you treated it as such.
Same issue – blank screens after update, delete via FTP and when attempting to install fresh WP says: “Plugin could not be activated because it triggered a fatal error”
Godaddy WP install.
Quick rescue is FTP or SSH. Rename
wp-content/plugins/jetpack/
to./_jetpack/
or whatever, so that JetPack is force-disabled.Then try to replace JetPack 4.8 with 4.7.1, and re-link it to www.ads-software.com.
- This reply was modified 7 years, 7 months ago by Tohru Murakami.
I just had to rename the plugin after updating so I am going to install the new plugin freshly after deleting the renamed plugin. Is this going to be the best resolve? I will follow this string to see. Thank you
Thanks Tohru good suggestion – this has worked for me, will be staying on 4.7.1 for a while I think.
Well, with FileZilla I renamed wp-content/plugins/jetpack
to wp-content/plugins/jetpack-old
Then I could get to the site’s login screen and logged in.
Went to Installed Plugins and deleted Jetpack.
Then added Jetpack 4.8 (the current version). After it installed I activated it.
Had to re-establish it’s connection with my wordpress.com account and now everything seems to be back on track.
Taking a quick check with FileZilla and I find my renamed folder jetpack-old is gone and the jetpack folder is there.
Did this on two sites I manage. So far so good.Well, Tiled Gallery disappeared from Jetpack. I have also a cookie error on /wp-json/jetpack/v4/settings (Bad Request error), my website is in HTTPS. I’m uploading the 4.7.1 version again… 4.8 is weird :/ !
Sorry about that! We’ve made some changes to the Sitemaps feature in Jetpack 4.8, and inadvertently used code that isn’t compatible with old versions of PHP (PHP 5.3 or less). If you get Fatal errors when using Jetpack’s Sitemaps module on yur site, that’s most likely what’s causing the issue.
We’ll release a new update to solve that problem, but until then I’m afraid I can only recommend the following:
- Contact your hosting provider and ask them if it is possible for you to use a more recent version of PHP. PHP 7 is the recommended version of PHP for WordPress, so if they can update you to PHP 7 that would be great.
- Remove the Jetpack plugin from your site until we release an update.
- Force Deactivate the Sitemaps module by installing this must-use plugin on your site. You can do so by following the instructions in the file.
Really sorry for all the trouble!
I’ll post again here once I have more news.
It seems that JetPack 4.8 requires PHP 7, otherwise it causes blank-screen errors (even in debug mode). JetPack 4.8 calls random_int(), which is available in PHP 7 and up
Jetpack 4.8 doesn’t require PHP 7. We aim to support PHP 5.2, although we’ve failed to do so in this last update, as I mentioned above.
random_int()
, however, is not at fault here. WordPress includes its own version ofrandom_int()
for folks who do not use PHP 7 yet:
https://developer.www.ads-software.com/reference/functions/random_int/
https://core.trac.www.ads-software.com/ticket/28633Well, as was stated in one of the replies to the above mentioned post, it now works!
I fixed it by accessing the site via FTP and disabling the JetPack plugin by renaming the plug-in folder.
I’m glad to hear that solved the issue for you! That means that the update didn’t complete properly, so some files were missing from your installation of Jetpack. Reinstalling from scratch allowed to get a full Jetpack plugin again.
Hi again,
Some news…
I have reinstalled Jetpack to 4.7.1
I have upgraded to PHP 7.0
I have a plugin, IP Geo Block that have a rule setting about the XML-RPC, I set that to disable, so now the The Jetpack server can communicate with my site again.When the connection where done, some new problems appeared. When I try to enable some Jetpack-features I got the Error: Cookie nonce is invalid. So I tried to deactivate WP Super Cache…that solved the problem with the Jetpack-features-error-message.
Everything seems to work again, but… Should i wait for the new Jetpack-update 4.8… before I update Jetpack again?
Cheers, AFPhoto
Sorry everyone for all the trouble! We’ve just released 4.8.1 to solve the issue mentioned in this thread.
You can read more about this release here:
https://wp.me/p1moTy-4N5Please update to 4.8.1 as soon as possible to see if that fixes that issue for you. Also, if you’re using WP Rocket, please update that to the latest version as well.
If you continue to experience issues, could you please try to delete the Jetpack plugin, and reinstall it from scratch? If that doesn’t help either, you can start a new thread here with as much information as possible about the errors you see on your site:
https://www.ads-software.com/support/plugin/jetpack#new-postThank you, and again, sorry for the trouble! While we do our best to test things prior to release, sometimes things fall through the cracks. We’ve added additional measures to make sure this type of error doesn’t happen again.
- The topic ‘Problems after update Jetpack’ is closed to new replies.