As draconian as the measure is, deleted the jetpack directory from my file manager and then re-installing it via the plugins page on the dashboard worked. I was getting a 500 error as well, but deleting the plugin directory jetpack stopped that, and reinstalling jetpack via the plugin page had version 1.6.1 working on the newest version of wordpress.
HTTP Error 500’s are usually web server issues. If you could look at your server error logs and find the messages associated with these errors, that would be helpful.
For what its worth, I have Jetpack and WP Filebase installed and active with no issue. The error seems to crop up if you install Jetpack’s files through WP filebase rather than through WordPress’s built-in mechanics.
Thanks for the response Tim. I am not sure what you mean by “install Jetpack’s files through WP filebase” but I did try installing WP Filebase through the WordPress Dashboard and via FTP.
It never worked correctly, so I just had to dump Jetpack and settle on Jetpack Lite; which works perfectly fine.
