Viewing 15 replies - 1 through 15 (of 29 total)
  • this seems to be happening on one of my sites as well, can not log into backend from custom url set up before the update.

    I have this same problem.

    It has something to do with the changes BWP Security makes to the .htaccess files.

    You can get to your Admin page again by removing the entire chunk that BWPS makes and then disabling the plugin. You can re-enable the plugin and let it write fresh entries back in, but the problem will come back at some point.

    Seems to have something to do with the automatic blacklisting entries. The site will go down after some of those get written and then bring itself back up after they’ve had a chance to expire back out, or if you manually wipe out the plugin’s entries.

    I’m looking for a permanent fix to this myself. I love the features of this plugin and have yet to find an alternative that’s its equal, I’d rather find a permanent solution that’s not “delete the plugin and use a different one”.

    So I don’t know how to get to my backups or anything since I’m getting this error on my backend and front page. ????

    Oh, and I use WordFence,.. NOT BWPS!

    Just popping in to say that this happens to me too.

    The stuff added to the htaccess is shutting down my whole site (gives me a 500 internal server error).

    I had to disable the plugin and delete all the extra htaccess entries to get it working again.

    I’m having the same issue. This is a BIG problem. Please HELP!!!

    Disabling the plugin/deleting the .htaccess stuff seems to be the only thing working (at the moment). Also, logging out seems to just lock out you completely out of the installation. If you’re reading this and haven’t upgraded yet – I would say, don’t.

    Same happen on my site also..for solution…

    Login via FTP and edit your .htacees file to locate and remove the below code:

    # BEGIN itheme Security

    All code in Between

    # End itheme Security

    And Change the folder name “wp-content/plugins/wp-better-security”

    to

    “wp-content/plugins/wp-better-security1”

    My Site LetHow is also facing the issue and get resolved temporary by above solution. Hope author will soon reply with more help to resolve the issue permanently…

    Help! Right after upgrade to iThemes my admin panel crashed!!
    I see this:
    Warning: require_once(/home/domain.name/wp-admin) [function.require-once]: failed to open stream: No such file or directory in /home/domain.name/wp-content/plugins/better-wp-security/core/class-itsec-lib.php on line 514

    Fatal error: require_once() [function.require]: Failed opening required ” (include_path=’.:/usr/local/lib/php:/usr/local/php5/lib/pear’) in /home/domain.name/wp-content/plugins/better-wp-security/core/class-itsec-lib.php on line 514

    How can I DOWNGRADE to BETTER WP security? I loved Better WP Security!! Please bring it back!

    P.S.: When I try to access admin panel via old secure link (Admin Slug) I see 404 error!

    All, it looks like ITheme Security just released their 4.0.1 release:

    According to the Changelog:

    “4.0.1

    Fix for issue whereas a blank deny ip line could be entered into wp-config.php during update if banned users was used.”

    I’m not going to update this until I see some proof it works…major #fail Better WP Security…

    On “upgrade” the .htaccess file has bad code in it that brings down the server.. to fix, try the following…

    If the beginning content in the file beginning of the file looks like:

    # BEGIN iThemes Security
    # BEGIN Ban Users
    Order allow,deny
    Deny from
    Deny from 176.53.65.71
    Deny from 141.138.204.113
    Allow from all
    # END Ban Users

    Remove the entire line that just has “Deny from” on it, so that it looks something like:

    # BEGIN iThemes Security
    # BEGIN Ban Users
    Order allow,deny
    Deny from 176.53.65.71
    Deny from 141.138.204.113
    Allow from all
    # END Ban Users

    Note, the IP addresses shown will likely be different for each site, and there could be many more of them, or none at all. Just remove the line indicated and leave the rest.

    Hope this helps.

    Having the same issue here. Removing all ithemes security related .htaccess entries fixes the issue. Did not have line containing only “Deny From” as Tim mentioned above, so couldn’t try that.

    Latest update fixes this issue. For safety, I deleted the entire contents of the plugin folder, downloaded the latest version, and uploaded all contents via FTP and reactivated. Works.

    Thanks, Tim Gary, it appears that the 4.0.1 release addresses that issue.

    I’ve isolated the issue to any rules related to banned users on my installation (not HackRepair.com’s blacklist).

    This actually isn’t addressed by 4.0.1. That updated fixes an issue where a blank line is inserted into wp-config.php, not .htaccess. I’m fairly certain there’s still an issue with the banned users .htaccess rules themselves. When I remove them the site is fine. When they’re included the site goes down. I’ve confirmed there is no blank line in wp-config.php.

Viewing 15 replies - 1 through 15 (of 29 total)
  • The topic ‘The page cannot be displayed because an internal server error has occurred error’ is closed to new replies.