The Community Forums

Interact with an entire community of cPanel & WHM users!
  1. This site uses cookies. By continuing to use this site, you are agreeing to our use of cookies. Learn More.

IPDeny mgr corrupts htaccess file

Discussion in 'General Discussion' started by biterg, Oct 22, 2010.

  1. biterg

    biterg Member

    Joined:
    Oct 22, 2010
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    I have a site where I have been adding a few IPs via the IPDeny manager in cPanel.
    The site uses cPanel v11.26.20_RELEASE_49708
    adding the IPs has corrupted the .htaccess file. The IPDeny mgr has been adding the blocked IPs after the closing tag of the <Files 403.shtml>......</Files> block. This has caused the site to respond with error 500 for all html requests.

    I manage several sites and have only seen this problem at one site with this cPanel version.

    One thing different is that, within the cPanel IPDeny manager, it will accept an IP range of..

    123.123.1.1 - 123.123.2.2 whereas all other versions choke because of the spaces each side of the dash.
    Others seem to only accept 123.123.1.1-123.123.2.2

    I usually use CIDR range settings, but not always.

    has anyone else seen this problem of cPanel messing up .htaccess?

    biterg.
     
  2. cPanelTristan

    cPanelTristan Quality Assurance Analyst
    Staff Member

    Joined:
    Oct 2, 2010
    Messages:
    7,623
    Likes Received:
    21
    Trophy Points:
    38
    Location:
    somewhere over the rainbow
    cPanel Access Level:
    Root Administrator
    Please open a support ticket using the link in my signature or using WHM > Support Center > Contact cPanel so we can see what is going on here. Since it's just one site, if you can give us the site in the ticket as well as another site where it isn't happening. We would want to see why the one site is exhibiting this behavior.
     
  3. biterg

    biterg Member

    Joined:
    Oct 22, 2010
    Messages:
    6
    Likes Received:
    0
    Trophy Points:
    1
    Fixed, I think

    I think I have found the problem and it looks like it was ME.

    I had a CIDR range loaded incorrectly , something like...

    123.45.6/12

    Looks like that upset the server and it returned the 500 errorcode
     
Loading...

Share This Page