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.

Can't access cpanel/whm

Discussion in 'General Discussion' started by edesignway, Jan 15, 2004.

  1. edesignway

    edesignway Well-Known Member

    Joined:
    Dec 4, 2001
    Messages:
    96
    Likes Received:
    0
    Trophy Points:
    6
    Can't access port 2082/2086

    Good Afternoon,

    I have run into a problem, I am unable to connect to port 2082 and 2086. I can connect to 2083 and 2087.

    I have tried /scripts/upcp, restarting cpanel, apache, /usr/local/cpanel/startstunnel

    When I run the command, lsof | grep 2082

    cpaneld 20687 root 5u IPv4 30568613 TCP *:2082 (LISTEN)

    When I run the command, lsof | grep 2086

    whostmgrd 20731 root 3u IPv4 30571223 TCP *:2086 (LISTEN)


    Any help you can offer will be greatly appreciated!

    Thank you,
    Timothy Sheehan
     
    #1 edesignway, Jan 15, 2004
    Last edited: Jan 15, 2004
  2. bjarne

    bjarne Well-Known Member

    Joined:
    Mar 23, 2002
    Messages:
    135
    Likes Received:
    0
    Trophy Points:
    16
    I have two servers who did not work with 2082 today (not realy 2083 either) with reeboot one is good the other one not.

    New problem something wrong?
     
  3. cyberultra

    cyberultra Member

    Joined:
    Oct 19, 2003
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    My problem is on some IPs 2086 is working fine but 2082 is not working.

    Any solution?
     
  4. edesignway

    edesignway Well-Known Member

    Joined:
    Dec 4, 2001
    Messages:
    96
    Likes Received:
    0
    Trophy Points:
    6
    Have you tired the following,

    /scripts/upcp
    restarting cpanel,
    restarting apache
    /usr/local/cpanel/startstunnel
     
  5. cyberultra

    cyberultra Member

    Joined:
    Oct 19, 2003
    Messages:
    16
    Likes Received:
    0
    Trophy Points:
    1
    Did all but problem still presists.

    Reboot server solved the problem for me ;)
     
Loading...

Share This Page