ISPconfig ports

Discussion in 'General' started by Squeazer, May 6, 2010.

  1. Squeazer

    Squeazer New Member

    I know this is kinda a stupid question, but which ports does ISPconfig use? I dont mean just ISPconfig, but the whole thing. (like 80 and 443 for apache). I dont realy want to go trough the entire thing to make a list of ports to forward, so if anyone has something like that already, please, post it :)
     
  2. Mark_NL

    Mark_NL New Member

    Code:
    netstat -tapn
    ?
     
  3. sikander

    sikander New Member

    port 80

    Hi All,

    I am new to linux and trying to configure high-availability HTTP cluster with heartbeat using the apache web server. I have one redhat machine on which i have configured to virtual machines as node1 and node2. I followed the instruction as it is given here.

    http://www.howtoforge.com/high_availability_heartbeat_centos

    When I try to start the httpd services on node1 it gives error.

    Starting httpd: (99)Cannot assign requested address: make_sock: could not bind to address 192.xxx.xxx.78:81
    no listening sockets available, shutting down
    Unable to open logs.

    and 78 is the main web server which is using port 80 and running and this node1 where i am trying to start httpd services it is giving error given above. I have tried to change the ports from 8o to any other port in httpd.conf but not working.

    Please give me some idea how can i solve this issue.

    Thanks in Advance.

    Regards,

    Sikander
     
  4. Mark_NL

    Mark_NL New Member

    Some process is already useing port 81,

    Code:
    netstat -tapn | grep '192.xxx.xxx.78:81'
    to see which process is using port 81

    stop that process, then start httpd, then start the process that was using port 81 before.

    Besides that, I don't want to demotivate you, but if you're new to linux .. don't you think setting up a HA httpd cluster is a tad over the top atm? Ofcourse everyone can copy paste everything from these excellent how-to's and everything works (that's what makes this site so nice) .. but don't forget that you try and understand WHAT you're doing, so when problems start arrising, you have some knowledge of what you have and what could cause the problem. The problem you're posting is basic linux / network / server knowledge, maybe start a bit easier?
     

Share This Page