Disable the plugin by logging in to your server using FTP and rename the “all-in-one-wp-security-and-firewall” plugin folder to another name – eg, “all-in-one-wp-security-and-firewall-temp“
Then FTP the .htaccess file to your computer and delete the code in between and including the following tags (if it exists):
# BEGIN All In One WP Security
# END All In One WP Security
Then FTP that modified file back to your server.
You should then be able to login.
I solved:
the question is NOT htacces nor AIOWSAF plugin nor wp-config.
The truth is that the “internal server error” message gives a fake impression of an unsuccessfull login only because the WP dashboard is not shown.
Reloading a page (any) of my WP site after a presumed failed login, I was surprised noticing that the admin bar whas up there. So admin was working, except its dashboard, which is the wp-admin/index.php file.
So, as AIOWSAF changed the file permissions for wp-admin/index.php from 755 to 644, I simply re-changed them to 755 for wp-admin/index.php
ALL is working again!
In conclusion I strongly suggest you to manage (and solve…) this problem, because it makes your valuable pluging not only unuseful, but really dangerous, if permissions for wp-admin/index.php are changed.
I don’t know if the problem is only mine due to my server-site-files… (and so on) conditions, by I spent 3 hours of work before understanding that the problem was so tiny. I risked to perform a complete backup, which would have resulted in a longer time loss, if not known the cause of the error.
Best of all.
AIOWSAF changed the file permissions for wp-admin/index.php from 755 to 644, I simply re-changed them to 755 for wp-admin/index.php
The plugin sets permissions to values which are “generally” considered secure for most server setups. However in some cases such as yours, the server may have a different or unusual setup which will of course need custom permission values to be set.
http://codex.ww.wp.xz.cn/Changing_File_Permissions
ps: You should probably try setting the wp-admin/index.php to 664 to see if that works.
Thanks for your reply.
Nor 664 is working: again produces “internal server error” after login or when opening WP dashboard. As concerns my server, it’s OK only if Execute permissions are granted at least to owner, so it works with 744.
I suggest anyway that in the Filesystem Security section of AIOWSAF won’t be suggested to change wp-admin/index.php permissions to 644; the login crash is quite dramatical. Anymore the solution to recover from the login crash (restore previous permissions to wp-admin/index.php) should be clearly explained, better if giving the possiblity of backuping and restoring this famous wp-admin/index.php file.
Best again
