After update: Jetpack could not be activated

Sorry about that!

Does the problem remain when you deactivate the Jetpack Lite plugin, and then reactivate Jetpack?

If so, could you add the following 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 );

}

Your wp-config.php file may already include a line that says “define(‘WP_DEBUG’, false);”. You can remove it, and replace it by the code above.

Once you’ve done so, try to activate the Jetpack plugin again to create the error and then check the wp-content/debug.log file for errors. You can paste the results here. You can then replace define('WP_DEBUG', true); by define('WP_DEBUG', false); in the code above.

Thanks!

I deactivated Jet Lite, but then, I couldn’t re-activate any the plugins.

Where do I find the Debug-Logfile?

Thanks!

Where do I find the Debug-Logfile?

That file will be created inside the wp-content folder in your WordPress installation as soon as an error is logged, like when you try to activate the plugin for example.

To access that file, you’ll need to access your site via FTP, or with a File Manager if your hosting provider offers that option.

Let me know what you find!

No, there is no Debugfile.

Eventually the problem is the activating-process?

I’m afraid I can’t really tel what the problem is, since there are no errors logged in the debug file.

Could you try to increase the amount of memory allocated to PHP on your site, as explained here, and let me know if it helps?

It’s working again!

After I deleted another plugin (ngg public upload, which isn’t supported since 2 days), the activation process is working again and so jetpack.
https://www.ads-software.com/support/plugin/nextgen-public-uploader

It wasn’t enough to deactivate this plugin, it had to be deleted.

Thanks for your support!

Excellent, I’m glad to hear you’re all set!