Viewing 14 replies - 16 through 29 (of 29 total)
  • yep happened to me too, i just disabled it, second time wp-security had this “update turns off site” kind of thing… pretty disappointing start! as of now its disabled on all my sites…

    The 4.0.1 should address the issue. Please contact me directly if you still see it. With over 100 sites personally upgraded and testing I have not been able to reproduce the error and I would love to see both the .htaccess and plugin conflict of anyone who is experiencing the problem with 4.0.1.

    As much as I would love to say I could test for every configuration out there, it just isn’t possible. That said, with a little data we’ll get to the bottom of it and fix it ASAP.

    Below are the rules that cause the problems for me. Removing them removes the problem. All other iThemes Security related rules are fine.
    The only other lines in my .htaccess are from W3TC.

    Order allow,deny
    		Deny from 101.64.0.0
    /8/16/16/16
    		Deny from 109.194.0.0
    /8/16/16/16
    		Deny from 109.87.0.0
    /8/16/16/16
    		Deny from 115.195.0.0
    /8/16/16/16
    		Deny from 123.152.0.0
    /8/16/16/16
    		Deny from 125.118.0.0
    /8/16/16/16
    		Deny from 134.249.0.0
    /8/16/16/16
    		Deny from 178.215.0.0
    /8/16/16/16
    		Deny from 178.94.0.0
    /8/16/16/16
    		Deny from 193.169.0.0
    /8/16/16/16
    		Deny from 194.146.0.0
    /8/16/16/16
    		Deny from 194.165.0.0
    /8/16/16/16
    		Deny from 37.45.0.0
    /8/16/16/16
    		Deny from 37.57.0.0
    /8/16/16/16
    		Deny from 41.107.0.0
    /8/16/16/16
    		Deny from 46.118.0.0
    /8/16/16/16
    		Deny from 60.176.0.0
    /8/16/16/16
    		Deny from 60.177.0.0
    /8/16/16/16
    		Deny from 77.123.0.0
    /8/16/16/16
    		Deny from 77.93.0.0
    /8/16/16/16
    		Deny from 79.135.0.0
    /8/16/16/16
    		Deny from 80.64.0.0
    /8/16/16/16
    		Deny from 94.153.0.0
    /8/16/16/16
    		Deny from 88.245.50.214
    		Allow from all

    I had to delete everything related to iTheme in the .htaccess file, including:

    # BEGIN iThemes Security
    # END iThemes Security

    My issue was resolved when removing the following line from .htaccess:

    Deny from

    That was causing an internal server error and none of my pages were loading.

    I’m still scrolling through all the comments but this “upgrade” from WP better security to the new ithemes security has already killed two of my websites completely. NOT exactly what we were looking for folks… This particular “upgrade” is so far an F-ing disaster. I’m disabling and removing wp better security on every site and looking for something else until this disaster is fixed.

    Try removing the lines in .htaccess related to banned hosts. That should get your site back online. They’ll probably roll out a permanent fix shortly.

    Thank you to Matt Zak for the data. I’ve fixed the issue and pushed version 4.0.2 to resolve. Also updated my unit tests with an extra test case (tested every combination of wildcard ip except multiple *s).

    Updated and it works fine for me. Thanks!

    Same! Updated to version 4.0.2 and everything went smoothly. ?? Thanks for the quick response to this issue!

    Since updating to 4.0.2 all seems good BUT each time I go to my WordPress Dashboard, I’m asked to log in as if I’d logged out five minutes ago. This is getting very annoying. Anyone else find this problem and a solution? I’m running on a Mac using WP 3.8.1

    Somehow the host I’m forced to use has the site on Microsoft-IIS/7.0. I’ve no idea how that works as I’ve never needed to go there. I get an internal server error and locked out. Will ftp in and run the backup. As you say, you can’t test on everything so this is an FYI
    Keep up the great work.

    By using this technique:
    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 iextremesports also faced a similar problem but resolved through this technique temporarily.

    I am having same problem.
    When i open my URL: https://www.piplia.com
    Error message displayed:The page cannot be displayed because an internal server error has occurred.

    Please help me!!!

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