Unable to Login – 500 Error

I have enabled the option to change the login URL to a custom one.

I think it’s on the latest version 7.7.1. It’s really frustrating to see that even after disabling the plugin, it didn’t worked.

You should check the web server log file for any additional (error) info.

Also there is very little info provided in this topic about your env so that makes it very hard to help you.

To prevent any confusion, I’m not iThemes.

Thank GOD I have some technical knowledge, manually edited the itsec_storage option value to disable the “hide-backend” feature and it worked.

Next thing, disabled the plugin for good.

Manually editing the itsec_storage option in the database is considered to be very risky. 1 small mistake can render your site useless/unstable.(Perhaps you have done this before in the past which makes me wonder about your env …)

It’s MUCH safer to make use of existing debugging functionality. You can temporarily disable all iTSec plugin modules by adding the line below to the wp-config.php file:

define('ITSEC_DISABLE_MODULES', true);

Did you check the web server log file for any additional (error) info as suggested ?

With a little more effort I’m sure we can fix the issue so you can continue to use a very usefull security plugin.

If you dismiss every plugin just because of one issue you end up some day without any plugin …

Just trying to be helpfull. Stay safe ??

Hi @nlpro

The direct config change in the database was obviously the last resort, thankfully it worked. Otherwise, I would have restored it from the backup, it’s not risky as long as you know what you are doing. Regarding my environment, I am on a non-managed Linode 40$ VPS, CentOS, CyberPanel+LSWS. I am managing it all by myself for the last 2 years.

I didn’t know about the ITSEC_DISABLE_MODULES option, but I did try all the debugging myself before taking the drastic step. There were no errors anywhere at all, the website was working fine, except the 500 error for wp-admin that lead me to immediately identify this plugin as the culprit. Even moving the better-wp-security folder from the plugins directory didn’t help. And, if I have to disable the modules then what is the use of it, better to disable the plugin itself.

I am not saying it’s a bad plugin, I might give it a try once again after a few more releases.

I am also okay to work through Developers if they need more information to debug the issue.