Redhat Apache 2.2.3 Not Loading

apache-2.2redhat

I have Apache 2.2.3 installed on this server, and when I try loading its webpage, it does not load. I just get a loading sign that it is trying to connect but no connection has been made.

I check the conf file and it is listening on all ips on port 80. It also has a proper vhost file as well as has a simple text html file for the index display "Test".

Some Additional Information:

It neither works for the domain or the ip address or even localhost from the server. I did a wget of localhost and got nothing

[root@server conf]# netstat -tulpn | grep ':80'
tcp        0      0 :::80                       :::*                        LISTEN      6256/httpd

My Apache conf: http://pastebin.com/MRDA8EkQ
Ip Tables Config: http://pastebin.com/nukXe5sD

Best Answer

It looks like your firewall needs to allow access on port 80 try

/sbin/iptables -I RH-Firewall-1-INPUT -p tcp -m tcp --dport 80 -j ACCEPT

and see if that works. If it does then save your firewall configuration with

/sbin/service iptables save

Related Solutions

Web-server – How to make Apache Web Server listen on two different ports

A standard Debian install of apache will have the following fragment of configuration:

Listen 80

<IfModule mod_ssl.c>
    # SSL name based virtual hosts are not yet supported, therefore no
    # NameVirtualHost statement here
    Listen 443
</IfModule>

This is telling apache to listen on port 80 and to listen to port 443 if mod_ssl is configured. In your case you'd want:

Listen 80
Listen 8080

You need to make sure you run a restart, not a reload operation on apache for it to pay any attention to new Listen directives. The safest thing to do is to stop apache, make sure it is dead and start it again.

If this configuration does not work, check the log files for any error messages. You could use "netstat -lep --tcp" to see if there is anything listening on port 8080. Finally, if everything else doesn't work, try running apache under strace to see if it's trying to bind to that port and failing, but not logging the problem.

Apache Startup Issues – Fixing Address Already in Use Error

You have another webserver running already. You have to stop or kill it before you can start Apache (or change one of them to a non-standard port, ie something other than port 80).

Best Answer

Related Solutions

Web-server – How to make Apache Web Server listen on two different ports

Apache Startup Issues – Fixing Address Already in Use Error

Related Topic