ISPConfig 3 on CentOS 6, ISPConfig not loading

Discussion in 'HOWTO-Related Questions' started by InspectahDeck, Jun 11, 2013.

  1. InspectahDeck

    InspectahDeck New Member

    I am following the tutorial here. I get to the part where you are supposed to install ISPconfig, which works fine. But upon finishing it says to open up xxx.xxx.xxx.xxx:8080, but mine does not load. I get a connection has timed out error. I did a nmap on port 8080 of my VPS IP, and it says STATE filtered. I have iptables stopped, and selinux disabled. Here is my netstat -tap.


    Code:
    Proto Recv-Q Send-Q Local Address               Foreign Address             State       PID/Program name
    tcp        0      0 *:tproxy                    *:*                         LISTEN      5227/httpd
    tcp        0      0 *:ftp                       *:*                         LISTEN      5254/pure-ftpd (SER
    tcp        0      0 server1.dkjensen.com:domain *:*                         LISTEN      4840/named
    tcp        0      0 localhost.localdomai:domain *:*                         LISTEN      4840/named
    tcp        0      0 *:ici                       *:*                         LISTEN      471/sshd
    tcp        0      0 localhost.localdomain:rndc  *:*                         LISTEN      4840/named
    tcp        0      0 localhost.localdomain:smtp  *:*                         LISTEN      718/sendmail
    tcp        0      0 *:https                     *:*                         LISTEN      5227/httpd
    tcp        0      0 *:imaps                     *:*                         LISTEN      3261/dovecot
    tcp        0      0 *:pop3s                     *:*                         LISTEN      3261/dovecot
    tcp        0      0 *:pop3                      *:*                         LISTEN      3261/dovecot
    tcp        0      0 *:imap                      *:*                         LISTEN      3261/dovecot
    tcp        0      0 *:webcache                  *:*                         LISTEN      5227/httpd
    tcp        0      0 *:http                      *:*                         LISTEN      5227/httpd
    tcp        0    316 server1.dkjensen.com:ici    173-10-93-222-BusName:25690 ESTABLISHED 789/sshd
    tcp        0      0 *:ftp                       *:*                         LISTEN      5254/pure-ftpd (SER
    tcp        0      0 *:domain                    *:*                         LISTEN      4840/named
    tcp        0      0 *:ici                       *:*                         LISTEN      471/sshd
    tcp        0      0 localhost.localdomain:rndc  *:*                         LISTEN      4840/named
    tcp        0      0 *:imaps                     *:*                         LISTEN      3261/dovecot
    tcp        0      0 *:pop3s                     *:*                         LISTEN      3261/dovecot
    tcp        0      0 *:pop3                      *:*                         LISTEN      3261/dovecot
    tcp        0      0 *:imap                      *:*                         LISTEN      3261/dovecot
    
     
  2. monkfish

    monkfish New Member

    Hello,

    From your netstat output you seem to have a http process listening on 8080 which may well be your ispconfig:

    Code:
    ..
    [B]tcp        0      0 *:webcache      *:*             LISTEN      5227/httpd[/B]
    ..
    Did you enable SSL? Do you get any difference if you use http or https to access?
    Have a poke in logs - maybe a "tail -f /var/log/httpd/error.log" in your console at same time as trying to access the page.

    Not important but last available doc issued was for centos 6.4 and is here install doc. Don't know if there might be any differences between the two.
     
  3. InspectahDeck

    InspectahDeck New Member

    Yes SSL is enabled, it makes no difference. The error log shows no relevant information to the error I am experiencing. Thanks for trying though!
     
  4. monkfish

    monkfish New Member

    Think about things then. If you're getting no entries in the error log are you getting entries in access log; ie is traffic getting through from your client wherever it is to the actual server.

    Perhaps a "tcpdump port 8080" to see if traffic is ACTUALLY hitting the box. If not, your problem is further back.

    Whilst this wont cause a page not to be displayed, particularly if you are connecting by ip address, you should also check your dns because the fqdn in your log does not resolve.
     

Share This Page