Fatal Error After Update

  • Resolved ibiza69

    (@ibiza69)


    3 years, 1 month ago

    Hi, we got in all our sites this fatal error after this last update:

    Fatal error: Uncaught Error: Class 'Automattic\Jetpack\Connection\Tokens' not found in /home/XXXXXX/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-client.php:75 Stack trace: #0 /home/XXXXXXXXX/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-client.php(26): Automattic\Jetpack\Connection\Client::build_signed_request(Array, '<?xml version="...') #1 /home/XXXXXXXXXX/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/legacy/class-jetpack-ixr-client.php(70): Automattic\Jetpack\Connection\Client::remote_request(Array, '<?xml version="...') #2 /home/XXXXXXXXX/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-sync/src/class-actions.php(409): Jetpack_IXR_Client->query('jetpack.syncAct...', Array) #3 /home/XXXXXXX/public_html/wp-includes/class-wp-hook.php(287): Automattic\Jetpack\Sync\Actions::send_data(Array, 'deflate-json-ar...', 1614754058.4444, 'sync', 0.0015299320220947, 0.0074660778045654, 4, '603f310a6a5bf') #4 in /home/XXXXXXXX/public_html/wp-content/plugins/jetpack/vendor/automattic/jetpack-connection/src/class-client.php on line 75

    Is there any way for solving this, we got 10 sites and in all of them got this error after updating, we have to make a rollback to v.9.4.1 and didn´t solve the problem, after ths update, it’s not possible to rollback versions, as the error keeps showing, this didn´t happen before update.

    Thank you.

Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    3 years, 1 month ago

    It would seem that the update was incomplete on your sites, or that caching is causing issues when looking for one of the new files that’s been added to your site.

    Could you try to install the latest version of Jetpack from scratch, and flush cache on your site?

    Could you all let me know if the error keeps happening on your site, or if it seemed to be a one-time error during the update process? It may indeed have been a temporary issue during the update process.

    Thank you!

    • This reply was modified 3 years, 1 month ago by Jeremy Herve.
    Thread Starter ibiza69

    (@ibiza69)

    3 years, 1 month ago

    Hi, we don´t have cache plugins installed.

    So, we have to unistall it completly? Then we have to reconfigure it in all our sites? Are you sure last version update was correct?

    Thanks for your help in advance 🙂

    Plugin Contributor Stef (a11n)

    (@erania-pinnera)

    3 years, 1 month ago

    Hi @ibiza69,

    All your data are stored in our servers, so deleting the plugin completely and reinstalling it from scratch won’t cause any “hard reset” in that sense.

    Let us know if this full reinstallation helps!

    As for the cache plugin, I’d recommend installing one; WP Super Cache is free, easy to install and set up, and it’s fully compatible with Jetpack and many other plugins:

    https://en-gb.wordpress.org/plugins/wp-super-cache/

    Give it a go and let us know if that helps too.

    It’d be great if you can also answer Jeremy’s question:

    Could you all let me know if the error keeps happening on your site, or if it seemed to be a one-time error during the update process? It may indeed have been a temporary issue during the update process.

    Thanks!

    Thread Starter ibiza69

    (@ibiza69)

    3 years, 1 month ago

    @jeherve, @erania-pinnera, none of the data was stored in your servers, we had to configurate all options again in one of our sites that we tested what you said, uninstall and reinstall plugin. We have to reconnect first back to wordpress.com, then reconfigurate all options back.

    And about your question @jeherve, the error was in all of our sites after updating plugin and trying to get last stable version back, both things gaved that error I showed you when I opened the thread.

    So now, seems we have to do all this same job in all of our sites, to each one, just for this update, when didn´t happen before…

    Thank you.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    3 years, 1 month ago

    the error was in all of our sites after updating plugin

    Did the error appear in your logs, or in an email you received about it, or did you see the error happening when trying to access all or specific pages on your site?

    If the error appeared in your logs, did it appear multiple times, or just once when you updated the plugin?

    Thread Starter ibiza69

    (@ibiza69)

    3 years, 1 month ago

    @jeherve it only appeared after updating Jetpack in all our sites at WP-Admin and not at FTP root or admin logs, plus WordPress health sended us an email about the error in each of the sites about this fatal error because Jetpack plugin.

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    3 years, 1 month ago

    @ibiza69 Thank you. In this case this was mostly a one-time error, that happened during the update process as the new files were being copied on your sites. It should not cause any further issues, you should be all set!

    Thread Starter ibiza69

    (@ibiza69)

    3 years, 1 month ago

    Thank you @jeherve. Have a nice time.

    sobeautystuff

    (@sobeautystuff)

    3 years, 1 month ago

    I have also received a fatal error but cannot access my dashboard at all to fix it. Any ideas on this?

    When seeking help with this issue, you may be asked for some of the following information:
    WordPress version 5.6.2
    Current theme: Massive Dynamic (version 6.1)
    Current plugin: Jetpack by WordPress.com (version 9.4)
    PHP version 7.3.27

    Website: http://www.sobeautystuffblog.com/

    errror: Fatal error: Namespace declaration statement has to be the very first statement or after any declare call in the script in /home4/sobeaut3/public_html/wp-content/plugins/jetpack/src/class-tracking.php on line 2

    I have received an email from wordpress with a “recovery mode” link, but this does not work either

    Plugin Author Jeremy Herve

    (@jeherve)

    Jetpack Mechanic 🚀

    3 years, 1 month ago

    @sobeautystuff The error you’re running into seems different, and happens with a different version of Jetpack.

    Could you try to log in to your site via FTP or CPanel, delete the existing Jetpack plugin folder, and reinstall the plugin from scratch?

    You’ll find the Jetpack plugin folder here:

    
wp-content
   plugins
     jetpack - DELETE THIS FOLDER

    If you’re not sure how to do this, you can ask your hosting company for help. They should also have documentation explaining how to edit or remove files from your site using FTP or a File Manager in your admin panel.

    Let me know how it goes.

    sobeautystuff

    (@sobeautystuff)

    3 years, 1 month ago

    Thank you so much, this worked, I’m back in! 🙂

    franciscus

    (@franciscus)

    3 years, 1 month ago

    I had the same error as the original poster on my test site.
    I hope you guys will fix this; I’ll hold off on updating the production sites for now.

    • This reply was modified 3 years, 1 month ago by franciscus.
Viewing 12 replies - 1 through 12 (of 12 total)
  • The topic ‘Fatal Error After Update’ is closed to new replies.