ljiljau

Thanks for the answer, but it started working without me doing anything in particular.
But first to answer to your last question.
Yes, internal server error occurred immediately after aiowps is being activated.

After aiowps deactivation we were able to login to admin dashboard. I tested it few more times, whenever aiowps is deactivated, login is possible. Deactivation of plugin is done through renaming it, as I have direct access to file system, we host our site on our own infrastructure, IIS and Windows Server 2012.

After few hours of aiowps being inactive/disabled, I activated it again and planning to continue troubleshooting next day, but it started to work normally. First thing I checked this morning is logging to our WordPress site, which went completely normal.

Just as a note, we have this plugin on our site from 2014. In the past there were some minor compatibility issues with aiowps and translate plugin, as we were using qtranslate, but it was solved very quickly.

• This reply was modified 7 years ago by ljiljau.

Hi there, I am having same issue.
After disabling plugin, login as admin is possible.
Funny thing is that everything has worked last week, and I haven’t done any updates, they are scheduled for today.
Error we are getting is pretty generic, internal server error. Through the AIO Security setting we didn’t change admin URL, it stayed WordPress generic.
When I try to activate again AIO Security through WordPress admin dashboard, I again get internal server error.
It seems that cannot find redirect_to path, which from (just as example) “https://example.com/wp-login.php” should redirect to “https://example.com/wp-login.php?redirect_to=https%3A%2F%2Fexample.com%2Fwp-admin%2F&reauth=1”, but when you disable plugin it clearly sees the path.

• This reply was modified 7 years ago by ljiljau.

Yesterday we updated polylang to version 2.0.1, we did not updated PHP, and it worked.

More information: we are using IIS 7, PHP 5.3.8, WordPress 4.5.3.
At the moment we are trying to update PHP to 5.4.

Same probleme here. After update to 2.0 polylang, our site reports 500 error, and only white pages. After renaming plugin folder, site is active and we are able to login trough wp-login. If we activate only polylang, it crushes again.