Wordfence Plugin issue – Staying in login page and don’t Entering to admin area

Hi @azamal, thanks for getting in touch.

Did you already follow the migration instructions from our help documentation? https://www.wordfence.com/help/advanced/remove-or-reset/#migrate-with-wordfence

I would be unable to troubleshoot JetPack plugin issues here, but it seems to me that the reason Wordfence originally would’ve had the problems you described could be because extended protection was still enabled from the previous site location, so your auto_prepend_file directive was either no longer present or pointing to a different location on your new web server. You can find and remove the directive youtself in your .users.ini or .htaccess file depending on which platform your previous server was running. It is possible that JetPack also will similarly have some ties to your old setup.

Thanks,

Peter.

Hi @wfpeter
Thank you for your answer,
no, actually I didn’t go by the instructions as our company bought this website from the other one, and I just transfer it to our server!
now we don’t have any access to them and the previous webserver has expired for a while.
I deactivated the Jetpack plugin from plugin folders on the server
and removed wordfence codes from .users.ini and.htaccess file,
the website is still up,
but after entering user & pass in the login page it keeps loading and loading and then the below error pops up:

Error 503 Backend fetch failed
Backend fetch failed

Guru Meditation:
XID: 32772

As the website is up and all internal pages are shown, I think this error is related to an overloaded login page which may back to the plugin issue!?
do you have any idea to solve this, please?

Hi @azamal,

A 503 Backend fetch failed is a web server error effectively stating that the server of the website isn’t functioning. As it only happens when signing in, it could be related to the credentials in your database migration being unreachable but I’ve even seen it in relation to caching or not enough memory too.

It’s not a specific Wordfence-branded error page therefore is probably related to some other configuration or element of the migration, but you could certainly try renaming /wp-content/plugins/wordfence plugin folder to “wordfence_bak” just to ensure the problem doesn’t come up because 2FA data from your previous site is unreachable or corrupt.

I would recommend contacting the server administrator or your host, whichever is appropriate in your case, to see if they can view the server and PHP error logs to see exactly what’s happening behind the scenes when the 503 is thrown.

Let me know how you get on!

Peter.