Title: Internal Server Error Last modified: August 22, 2016 --- # Internal Server Error * Resolved [wordruppress](https://wordpress.org/support/users/wordruppress/) * (@wordruppress) * [11 years, 6 months ago](https://wordpress.org/support/topic/internal-server-error-265/) * after installing All In One WP Security & Firewall **login is off**. Nor users, nor administrator ara able to login. Login results in a blank page with: ————- Internal Server Error The server encountered an internal error or misconfiguration and was unable to complete your request. Please contact the server administrator,…. @rupestre…. and inform them of the time the error occurred, and anything you might have done that may have caused the error. More information about this error may be available in the server error log. ————- * I can’t disable plugins because I can’t enter, the site is on but administration is off… before loosing hours to restore a backuo I would like to know if there is a solution. * Restoring .htacces doesn’t work, nor wop-congfig * It the first time that a plugin gives so hard problems.. I hope you know what are you doing! * [https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/) Viewing 4 replies - 1 through 4 (of 4 total) * Plugin Contributor [wpsolutions](https://wordpress.org/support/users/wpsolutions/) * (@wpsolutions) * [11 years, 6 months ago](https://wordpress.org/support/topic/internal-server-error-265/#post-5525328) * 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. * Thread Starter [wordruppress](https://wordpress.org/support/users/wordruppress/) * (@wordruppress) * [11 years, 6 months ago](https://wordpress.org/support/topic/internal-server-error-265/#post-5525332) * **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. * Plugin Contributor [wpsolutions](https://wordpress.org/support/users/wpsolutions/) * (@wpsolutions) * [11 years, 6 months ago](https://wordpress.org/support/topic/internal-server-error-265/#post-5525337) * > 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.wordpress.org/Changing_File_Permissions](http://codex.wordpress.org/Changing_File_Permissions) * ps: You should probably try setting the wp-admin/index.php to **664** to see if that works. * Thread Starter [wordruppress](https://wordpress.org/support/users/wordruppress/) * (@wordruppress) * [11 years, 6 months ago](https://wordpress.org/support/topic/internal-server-error-265/#post-5525338) * 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 Viewing 4 replies - 1 through 4 (of 4 total) The topic ‘Internal Server Error’ is closed to new replies. * ![](https://ps.w.org/all-in-one-wp-security-and-firewall/assets/icon-256x256. png?rev=2798307) * [All-In-One Security (AIOS) – Security and Firewall](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/) * [Frequently Asked Questions](https://wordpress.org/plugins/all-in-one-wp-security-and-firewall/#faq) * [Support Threads](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/) * [Active Topics](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/active/) * [Unresolved Topics](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/unresolved/) * [Reviews](https://wordpress.org/support/plugin/all-in-one-wp-security-and-firewall/reviews/) ## Tags * [login](https://wordpress.org/support/topic-tag/login/) * [server](https://wordpress.org/support/topic-tag/server/) * 4 replies * 2 participants * Last reply from: [wordruppress](https://wordpress.org/support/users/wordruppress/) * Last activity: [11 years, 6 months ago](https://wordpress.org/support/topic/internal-server-error-265/#post-5525338) * Status: resolved