WORDFENCE CAUSE BACKEND SLOW AND FREQUENT CRASH

Hey @giuliosensi,

Can you please check the PHP error logs for any relevant errors? This might give us an idea of what’s going on.

You might also try resetting Wordfence to see if it helps.

https://www.wordfence.com/help/advanced/remove-or-reset/#remove-or-reset

Do you recall which plugins you updated when this started happening?

Thanks,

Gerroald

Hello Gerroald, thanx for your quick answer

we made a complete web restyle .. so we changed Theme, added some plugins deleted others… it’s hard to wonder conflict responsible one..

We made some test and we got this ..

2020/05/22 15:03:36 [error] 23#23: *603276 upstream timed out (110: Operation timed out) while reading response header from upstream, client: 172.20.0.1, server: masacoustics.it, request: “GET /wp-admin/admin-ajax.php?action=wpseo_get_facebook_name&_ajax_nonce=1bd0c5a995&user_id=1 HTTP/1.0”, upstream: “fastcgi://unix:/var/run/masa.sock”, host: “www.masacoustics.it”, referrer: “https://www.masacoustics.it/wp-admin/post.php?post=19996&action=edit”

Seems to be a Yoast issue…

Funny thing that Disabling Yoast solves the problem…
But also disabling Wordfence solves the problem.

Things are getting better using HEARTBEAT on backend since seems it’s admin-ajar related problem…

Hey @giuliosensi,

Thanks for the update, and information.

Can you please try completely setting Wordfence and Yoast to see if it helps? There are many, many people using both plugins without issue.

Please let me know.

Thanks,

Gerroald

Hello Gerroald I tried a reset with WF Assistant, deleted and reinstalled plugin but some of the settings remained unchanged.

Now also with heart beat I get some problems..

Hey @giuliosensi,

The settings really shouldn’t have remained. It’s possible there are some database permissions issues here. Can you try resetting Wordfence once more, but using the manual method and let me know how it goes? If this doesn’t help, I’ll bump the developers for their thoughts.

Thanks,

Gerroald

Hello I succeded in performing a complete WF RESET , unfortunately this not helps.

I’m making many tests. I recently discovered that:

Disabling YOAST don’t always solve the problem

Disabling WORDFENCE always solves the problem

I got 504 almost always when for example :

Modifying a page and then saving
Modifying a article and then saving
create a coupon code and then saving.
Oter BACKEND TASKS

My webmaster telo me that problem can be related on AJAX_ADMIN

Even Installing Heartbeat do not helps ..

UPDATE … I discovered that HEARBEAT CONTROL was not set correctly … now it seems thing are better, I will continue testing !!

Ciao !

Giulio

Hey @giuliosensi,

Thanks for the update, and happy to hear you’re tracking it down. If disabling Wordfence doesn’t help every time the trouble is going to be elsewhere, as you’ve discovered.

Please do let us know if anything else comes up.

Thanks,

Gerroald

Hello , no I confirm you that :

Disabling YOAST don’t always solve the problem
Disabling WORDFENCE

always solves the problem

So it seems it’s WORDFENCE related but actually seems to be more stable using Heartbeat plugin

Ciao !

Giulio