Originally Posted by Anderl
I got to change port in 'Listen 80' because with port 80 I got error of Apache.
I'm almost certain that this is a bad idea - as far as I understand it, this means that no web browser will connect to your website by default, because they will try to connect with port 80.
I think a more likely fix is to change it back to 'listen 80' and find and kill the process which is binding to 80 already. http://www.linuxquestions.org/questi...7/#post2474057
talks of the same problem (ey have got a subdomain setup too) and mentions as a fix removing the 'listen' line altogether - which you could try, but as ey mention in their post, I don't know whether that's just a kludge.
To work out what's listening on what port, run:
sudo netstat -ltnup
My output looks like:Active Internet connections (only servers)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 127.0.0.1:31416 0.0.0.0:* LISTEN 351/boinc_client
tcp 0 0 0.0.0.0:17500 0.0.0.0:* LISTEN 2293/dropbox
tcp6 0 0 :::80 :::* LISTEN 5651/httpd
udp 0 0 0.0.0.0:17500 0.0.0.0:* 2293/dropbox
udp 0 0 172.16.112.40:123 0.0.0.0:* 784/ntpd
udp 0 0 127.0.0.1:123 0.0.0.0:* 784/ntpd
udp 0 0 0.0.0.0:123 0.0.0.0:* 784/ntpd
udp6 0 0 ::1:123 :::* 784/ntpd
udp6 0 0 fe80::224:1dff:fe84:123 :::* 784/ntpd
udp6 0 0 :::123 :::* 784/ntpd
so you can see httpd (apache for you) listening on port 80 (the :::80)
EDIT: Also just found the docs for the VirtualHost directive: http://httpd.apache.org/docs/2.2/vhosts/examples.html
the 'listen' line seems to be a good'un, but it may be worthwhile comparing the relevant sections of your httpd.conf...
Hope this helps,