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.

What should I not touch at the command line

Discussion in 'Data Protection' started by yeohbaby, Nov 26, 2004.

  1. yeohbaby

    yeohbaby Member

    Joined:
    Nov 25, 2004
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    1
    New to cpanel, but have a little experience configuring the system at the command line. Is there anything that should not be touched at the command line because it will break cpanel?

    Given my unfamiliarity, it is still easier for me to configure some stuff at the command line.

    TIA
     
  2. sawbuck

    sawbuck Well-Known Member

    Joined:
    Jan 18, 2004
    Messages:
    1,367
    Likes Received:
    5
    Trophy Points:
    38
    cPanel Access Level:
    Root Administrator
    Only suggestion would be to first make a backup of whatever you intend to edit.
     
  3. chirpy

    chirpy Well-Known Member

    Joined:
    Jun 15, 2002
    Messages:
    13,475
    Likes Received:
    20
    Trophy Points:
    38
    Location:
    Go on, have a guess
    I'd go along with that too :)

    I'd also suggest that you don't mess around with your kernel - practice on a home PC first ;) Other than that, so long as you backup first you should be OK.

    Oh, be especially careful if you play with SSH and/or installing an iptables firewall like APF. Both can end up with support requests to your NOC if you're not careful :)
     
  4. yeohbaby

    yeohbaby Member

    Joined:
    Nov 25, 2004
    Messages:
    24
    Likes Received:
    0
    Trophy Points:
    1
    ok. Not planning on playing with the kernel just yet.

    Any recommended settings for APF to work properly with ServerBeach and not break access to cpanel?
     
  5. dalem

    dalem Well-Known Member
    PartnerNOC

    Joined:
    Oct 24, 2003
    Messages:
    2,577
    Likes Received:
    40
    Trophy Points:
    48
    Location:
    SLC
    cPanel Access Level:
    DataCenter Provider
    conf.apf these are mine you may need to add some ports depending on what ports you are using and if server beach uses a certtain port for monitoring

    # Common drop ports; these are implicit ports you do not want logged
    # with the default drop chains. Format is comma seperated and underscore
    # seperator for ranges (135_139). Ports are droped and ignored for both
    # TCP & UDP as well as inbound and outbound.
    CDPORTS="135_139,111,161,199,513,445,1434,1234,1524"


    # Common ingress (inbound) TCP ports
    IG_TCP_CPORTS="21,22,25,53,80,110,143,995,443,2082,2083,2084,2086,2087,2089,2095,2096,30000_35000,"


    # Common ingress (inbound) UDP ports
    IG_UDP_CPORTS="53"

    # Common egress (outbound) TCP ports
    EG_TCP_CPORTS="21,25,80,443,43"
     
Loading...

Share This Page