Same here. However, one caveat I’ll include is that I’ve had this happen on 3 sites. Disabling Wordfence does in fact bring back the dashboard. On two of the sites however, disabling Jetpack or Event Calendar would also bring the site back. Sites A and B had Jetpack in common. Sites A and C had Event Calendar in common. All three had Wordfence.
Thread Starter
harpon
(@harpon)
Our host is Siteground and we have been using WF with WP for over a year on 10+ sites. I tracked down that the comments module of Jetpack and the Siteground optimiser was the cause of the conflict on one of the sites. Strangely today on that site everything is working with everything enabled again. The other two sites are still only working with extended protection disabled. I will investigate further when I have time.
I had the same issue with WPML.
If I enble both WPML and Wordfence I loose access to dashboard.
Disabling either WPML or Wordfence resolves the problem.
I’m also hosted on Siteground.
I tired disabling extended protection, custom urls, full firewall but nothing worked, only disabling plugin helps.
-
This reply was modified 8 years, 10 months ago by
mumu9.
-
This reply was modified 8 years, 10 months ago by mumu9.
Hi guys!
Thanks for reporting this. I think it may be related to a current bug in Jetpack but I am not sure. We didn’t change anything in the latest release that should have caused anything like this. I will investigate a bit and get back to you asap.
In my case it was a memory error fixed by Siteground support.
Hi im also having issues on my site.
initially i posted here but i thought it would be best if i create a new post
You can ask Siteground support for help.
Anyway this is the php.ini that’s working for me after they adjusted the values:
opcache.interned_strings_buffer = 16
auto_prepend_file = "/home/[user]/public_html/wordfence-waf.php"
I don’t know what’s your specific plan so it could work or not, you’d better ask them before!
Thread Starter
harpon
(@harpon)
Thanks @mumu9
The problem was with Siteground hosting and not WF, sorry WF.
Adding opcache.interned_strings_buffer = 16 to the php.ini fixes the 500 server errors.
Thanks for the updates guys! Very helpful. I’ll make sure the team knows in case more people ask for help about this.
