Lots of things can cause that and the JetPack support guys can no doubt help you get it going, but they don’t generally work on the weekends, so if you want to get back into your site before they can help, you can use FTP or another file manager your host provides, to delete the jetpack folder here:
wp-content
plugins
jetpack
Might be related to your other thread?
https://wordpress.org/support/topic/internal-server-error-500-for-non-admins?replies=3
Thread Starter
Shan
(@gilmore_love)
its not related to that coz that issue has been resolved after disabling the cloudflare.
im using W3 cache now.
Glad you got that one sorted, but W3TC is known to be problematic with JetPack –
http://jetpack.me/support/getting-started-with-jetpack/known-issues/
Thread Starter
Shan
(@gilmore_love)
still the same issue after disabling the W3 also. do i have to remove W3 and try it?
Thread Starter
Shan
(@gilmore_love)
i found this in .htaccess
# Rules to block suspicious URIs
RewriteCond %{QUERY_STRING} !^action=jetpack-sso
Have you managed to solve the issue by yourself? Do you still get a 500 error after installing the plugin?
If so,could you check your server error logs around the time when you experienced the issue, to find out more about the error?
If you don’t know how to access your server error logs, your hosting provider should be able to help.
Let me know how it goes.
i found this in .htaccess
# Rules to block suspicious URIs
RewriteCond %{QUERY_STRING} !^action=jetpack-sso
Do you know which plugin added this line to your .htaccess file? If not, could you tell me what other plugins are currently active on your site?
Thanks!
everytime I activate Jetpack on one of my multisite installations and connect it to a WordPress.com account it crashes the site for a minute or two – I do use cloudflare
@wasanajones I’m sorry to hear you’ve run into issues.
Could you check your server error logs around the time when you experienced the issue, to find out more about the error?
If you don’t know how to access your server error logs, your hosting provider should be able to help.
Let me know how it goes.
Hi,
I will try to revive this post as I am running into the same issue:
Wordpress 4.1.1 – some plugins but no caching ones.
Install JetPack – no problem
Connect to WordPress.com: Fatal PHP Error;
Tried this twice: both times renaming plugins/jetpack resolves the issue. Both time the error is the following:(From cpanel Error Log)
Haven’t noticed the issue in older installs with Jetpack connected; But I will not update Jetpack untill I hear back.
[Tue Feb 24 06:02:23.411084 2015] … PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30720 bytes) in /public_html/wp-includes/class-IXR.php on line 1056
[Tue Feb 24 05:33:17.088940 2015] … PHP Fatal error: Allowed memory size of 67108864 bytes exhausted (tried to allocate 30720 bytes) in /public_html/wp-includes/class-IXR.php on line 331
Thank you
Daveed
Plugin Contributor
Ryan C.
(@ryancowles)
No problem; 4 weeks no response from OP, I thought it would be good to revive.
In any case it seems that upping the memory for the account took care of the error. Although 64M should be fine; in this case 96M was required. Just wondering if the memory requirements for Jetpack have changed? Specifically during the authentication process.
Over and out
Daveed
Plugin Contributor
Ryan C.
(@ryancowles)
Hi Daveed,
I’m glad to hear that you were able to resolve the issue, and thanks for the information! I’m not aware of any recent changes in Jetpack that would require upping the memory. Have you made any other changes to your site or server config recently?
Nope. It was a new site.
But on the same server I host maybe 12 installs with the approximately same number and type of plugins, and this is the first time for this error. Even upgraded Jetpack on most of them.
Thanks
Daveed
Plugin Contributor
Ryan C.
(@ryancowles)
Thanks again for the additional information. Since it seems to be an isolated incident, I’m not sure if there’s much more we can do at the moment. However, if you run into any further trouble, please don’t hesitate to let us know!
I know this is an old one but I just hit the same problem and found a fix:
In my case, another plugin called “WP Htaccess Editor” wrote some old order/deny rules in /wp-content/.htaccess and this was throwing a server error at some jetpack/_inc and after-deadline/tinymce content (!)
Only after looking at the /var/log/apache2/error.log and noted that cloudflare was using at least 4 IPs to reach my website, I understand what was going on.
