LINUX Web site not visible outside the host

butchrappe · 12-16-2012, 04:18 PM

Long story short - we were using FEDORA12, then web site busted - for reasons unknown. Update to Fedora 16, 17 didn't improve anything, since we couldn't get apache working. Now on CENTOS 6.3, and EVERYTHING appears to be working just fine - except we can't see the web site outside the hose. On the host - it looks like it knows it's www.xxxx.com However none of the machines on the local net can see it (and naturally, no one outside the DSL either). We have DSL modem, thence to our net router and the net below it. Firewall has been enabled for 80 and 443 and a few others for printing (which works). Apache starts on boot - everything looks fine. So how-to get the web site out to the world?

Thanks much for any assist. This has really drained time and money.

chrism01 · 12-16-2012, 05:25 PM

Can you post the httpd.conf? It may only be listening on 127.0.0.1.
Show

Code:

iptables -nvL

#OR
cat /etc/sysconfig/iptables


#AND
netstat -tanp

butchrappe · 12-16-2012, 07:00 PM

Here's the iptables and the netstat:
[root@www ~]# iptables -nvL
Chain INPUT (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT udp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:53
0 0 ACCEPT tcp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:53
0 0 ACCEPT udp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 udp dpt:67
0 0 ACCEPT tcp -- virbr0 * 0.0.0.0/0 0.0.0.0/0 tcp dpt:67
1985 1086K ACCEPT all -- * * 0.0.0.0/0 0.0.0.0/0 state RELATED,ESTABLISHED
0 0 ACCEPT icmp -- * * 0.0.0.0/0 0.0.0.0/0
4 240 ACCEPT all -- lo * 0.0.0.0/0 0.0.0.0/0
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:993
42 8911 ACCEPT udp -- * * 0.0.0.0/0 224.0.0.251 state NEW udp dpt:5353
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:631
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:631
0 0 ACCEPT udp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW udp dpt:631
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:443
0 0 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:22
12 628 ACCEPT tcp -- * * 0.0.0.0/0 0.0.0.0/0 state NEW tcp dpt:80
341 70344 REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- * virbr0 0.0.0.0/0 192.168.122.0/24 state RELATED,ESTABLISHED
0 0 ACCEPT all -- virbr0 * 192.168.122.0/24 0.0.0.0/0
0 0 ACCEPT all -- virbr0 virbr0 0.0.0.0/0 0.0.0.0/0
0 0 REJECT all -- * virbr0 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable
0 0 REJECT all -- virbr0 * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-port-unreachable
0 0 REJECT all -- * * 0.0.0.0/0 0.0.0.0/0 reject-with icmp-host-prohibited

Chain OUTPUT (policy ACCEPT 2261 packets, 367K bytes)
pkts bytes target prot opt in out source destination

[root@www ~]# netstat -tanp
Active Internet connections (servers and established)
Proto Recv-Q Send-Q Local Address Foreign Address State PID/Program name
tcp 0 0 0.0.0.0:41609 0.0.0.0:* LISTEN 2390/rpc.statd
tcp 0 0 0.0.0.0:111 0.0.0.0:* LISTEN 2220/rpcbind
tcp 0 0 192.168.2.10:80 0.0.0.0:* LISTEN 2722/httpd
tcp 0 0 192.168.122.1:53 0.0.0.0:* LISTEN 2889/dnsmasq
tcp 0 0 0.0.0.0:22 0.0.0.0:* LISTEN 2582/sshd
tcp 0 0 127.0.0.1:631 0.0.0.0:* LISTEN 2452/cupsd
tcp 0 0 127.0.0.1:25 0.0.0.0:* LISTEN 2678/master
tcp 1 0 192.168.2.10:41348 69.30.155.88:80 CLOSE_WAIT 3521/clock-applet
tcp 0 0 :::5989 :::* LISTEN 2836/cimservermain
tcp 0 0 :::42090 :::* LISTEN 2390/rpc.statd
tcp 0 0 :::5900 :::* LISTEN 3315/vino-server
tcp 0 0 :::111 :::* LISTEN 2220/rpcbind
tcp 0 0 :::22 :::* LISTEN 2582/sshd
tcp 0 0 ::1:631 :::* LISTEN 2452/cupsd
tcp 0 0 :::443 :::* LISTEN 2722/httpd

How-to attach a file? I can provide httpd.conf.
It's listening on www.xxxx.com:80

On a computer on our local net, I can get the home page by entering the address 192.168.2.10. But, it doesn't go to any of the links because the www.xxx.com isn't known outside
the server.

Let me know if httpd.conf will help, I cna try to copy the text for you as I did the info above.

Thanks much.

Butch

frankbell · 12-16-2012, 08:36 PM

Have you tried any diagnostics from a remote computer, such as

Code:

ping [domain name]
whois [domain name]
traceroute [domain name]

and what were the results?

Assuming that (1) it worked before, that (2) port 80 is open to receive requests, and that (3) port forwarding is properly configured in your router, my next guess would be that the "A" record either doesn't exist or is malformed.