ISPConfig running...but port 81 not listening

Discussion in 'Installation/Configuration' started by SoMBS, Sep 14, 2007.

  1. SoMBS

    SoMBS New Member

    I recently installed Ubuntu and ISPConfig and had it running just fine. Accessed ISPConfig server on port 81 without issue. Now suddently I can not connect. netstat -tap doesn't show port 81 listening any longer. Restarted ispconfig_server still no good. Rebooted server...no good. I'm not sure what could have changed to cause this. Any suggestions?
     
  2. chuckl

    chuckl New Member

    If there is nothing listening on port 81, then the IspConfig server is not running.
    Check the syslog /var/log/syslog, or the Ispconfig server log - /root/ispconfig/httpd/logs
     
  3. SoMBS

    SoMBS New Member

    I checked the syslog files and no entry about a warning or that ISPConfig is running or not running. So I started it and it returned it's now running. Output of netstat -tap below indicates it's not. The most recent thing I was doing was setting the server up to listen on port 8000 and added that to apache. Not sure if or why that would could this.

    /etc/init.d/ispconfig_server start
    Starting ISPConfig system...
    /root/ispconfig/httpd/bin/apachectl startssl: httpd started
    ISPConfig system is now up and running!

    netstat -tap
    Active Internet connections (servers and established)
    Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
    tcp 0 0 *:8000 *:* LISTEN 2850/apache2
    tcp 0 0 localhost.localdom:2208 *:* LISTEN 4785/hpiod
    tcp 0 0 *:mysql *:* LISTEN 4902/mysqld
    tcp 0 0 *:www *:* LISTEN 2850/apache2
    tcp 0 0 *:ftp *:* LISTEN 3047/proftpd: (acce
    tcp 0 0 server1.varnet.c:domain *:* LISTEN 3010/named
    tcp 0 0 localhost.locald:domain *:* LISTEN 3010/named
    tcp 0 0 localhost.localdoma:ipp *:* LISTEN 30407/cupsd
    tcp 0 0 localhost.localdoma:953 *:* LISTEN 3010/named
    tcp 0 0 *:smtp *:* LISTEN 2956/master
    tcp 0 0 *:https *:* LISTEN 2850/apache2
    tcp 0 0 localhost.localdom:2207 *:* LISTEN 4793/python
    tcp 0 0 localhost.localdoma:953 localhost.localdo:53825 TIME_WAIT -
    tcp6 0 0 *:imaps *:* LISTEN 5054/couriertcpd
    tcp6 0 0 *:pop3s *:* LISTEN 5095/couriertcpd
    tcp6 0 0 *:pop3 *:* LISTEN 5070/couriertcpd
    tcp6 0 0 *:imap2 *:* LISTEN 5030/couriertcpd
    tcp6 0 0 *:domain *:* LISTEN 3010/named
    tcp6 0 0 *:ssh *:* LISTEN 5233/sshd
    tcp6 0 0 ip6-localhost:953 *:* LISTEN 3010/named
    tcp6 0 0 *:smtp *:* LISTEN 2956/master
     
  4. SoMBS

    SoMBS New Member

    Well I went in a commented out the line Listen 8000 in root/ispconfig/httpd/conf - httpd.conf and now it's running. I also have port 8000 listening correcty now it seems. See netstat -tap below.

    tcp 0 0 *:8000 *:* LISTEN 4463/apache2
    tcp 0 0 localhost.localdom:2208 *:* LISTEN 4785/hpiod
    tcp 0 0 *:mysql *:* LISTEN 4902/mysqld
    tcp 0 0 *:www *:* LISTEN 4463/apache2
    tcp 0 0 *:81 *:* LISTEN 4426/ispconfig_http
    tcp 0 0 *:ftp *:* LISTEN 4680/proftpd: (acce
    tcp 0 0 server1.varnet.c:domain *:* LISTEN 4640/named
    tcp 0 0 localhost.locald:domain *:* LISTEN 4640/named
    tcp 0 0 localhost.localdoma:ipp *:* LISTEN 30407/cupsd
    tcp 0 0 localhost.localdoma:953 *:* LISTEN 4640/named
    tcp 0 0 *:smtp *:* LISTEN 4583/master
    tcp 0 0 *:https *:* LISTEN 4463/apache2
    tcp 0 0 localhost.localdom:2207 *:* LISTEN 4793/python
    tcp 0 0 localhost.localdoma:953 localhost.localdo:50002 TIME_WAIT -
    tcp6 0 0 *:imaps *:* LISTEN 5054/couriertcpd
    tcp6 0 0 *:pop3s *:* LISTEN 5095/couriertcpd
    tcp6 0 0 *:pop3 *:* LISTEN 5070/couriertcpd
    tcp6 0 0 *:imap2 *:* LISTEN 5030/couriertcpd
    tcp6 0 0 *:domain *:* LISTEN 4640/named
    tcp6 0 0 *:ssh *:* LISTEN 5233/sshd
    tcp6 0 0 ip6-localhost:953 *:* LISTEN 4640/named
    tcp6 0 0 *:smtp *:* LISTEN 4583/master
     
  5. chuckl

    chuckl New Member

    I suspect you had the IspConfig server and the apache2 server both attempting to listen on port 8000, and the Apache2 main webserver got in first.
     
  6. SoMBS

    SoMBS New Member

    Yeah it seems so. Now I only have the ports.conf file in apache2 directory listening on port 8000 in addition to port 80 and 443. This is working the way I need it to. Good learning situation. Thanks for your feedback.
     

Share This Page