Skip to content


Subversion checkout URL

You can clone with
Download ZIP


Can't update Jetpack #781

mpeshev opened this Issue · 3 comments

2 participants


I've tried updating Jetpack on a local install from 2.0.2 to latest with

wp plugin update jetpack

After waiting for several minutes I got this message:

Warning: The package could not be installed. PCLZIP_ERR_BAD_FORMAT (-10) : Unable to find End of Central Dir Record signature

This is coming from WP and the forums suggest that it's usually related to incorrect extract from the archive, usually due to the lack of disc space, but I have some 200 gigs here so it's not this.

It works for other plugins so it's not a permission issue as well.

This might be completely a WP/Jetpack issue, but wanted to note it as it could be due to some timeout or something like that (other plugins take 2-5sec to update).


Can't reproduce:

User@air:wp$ wp core version
User@air:wp$ wp plugin install jetpack --version=2.0.2
Installing Jetpack by (2.0.2)
Downloading install package from
Unpacking the package...
Installing the plugin...
Plugin installed successfully.
User@air:wp$ wp plugin update jetpack
Success: Updated 1/1 plugins.
Enabling Maintenance mode...
Downloading update from
Unpacking the update...
Installing the latest version...
Removing the old version of the plugin...
Plugin updated successfully.
Disabling Maintenance mode...

Does downloading the zip manually and running wp plugin install work?


Now I think it might be related to the fact that wp-content is outside of the WP directory. It works for the other plugins and wp plugin list returns the results, but the installer says that the directory no longer exists.

It still works for the other plugins, maybe some edge case with timeout + trying to install in the wrong place after that.


I was able to update properly now, my only guess leaves the timeout issue with incomplete or wrong download after some time (when the connectivity is wonky and it takes longer to download).

@mpeshev mpeshev closed this
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.