kwatog

I’ve been encountering this for a number of times already and on each time, I had to upgrade WordPress manually(through SSH to make it faster). Now, I was able to partially solve this by removing/renaming the existing upgrade folder under wp-contents. You can follow the steps below.

1. Login to your server via FTP
2. navigate to wp-contents folder
3. rename the existing upgrade folder to a new name(you can also choose to delete)
4. under wp-contents folder, create a new folder named upgrade
5. set permission of the new upgrade folder to 666
6. re-run the upgrade from within wordpress

Read more…