Welcome to WebmasterWorld Guest from 54.196.224.166

Forum Moderators: bakedjake

Message Too Old, No Replies

Cannot access Apache outside local network

ping and localhost positive, but no outside network access.

     

buckminster1

3:09 am on Dec 21, 2008 (gmt 0)

5+ Year Member



Did not see the Linux section - this is a repost from the Apache main topic (sorry)

I have a fresh Ubuntu 8.04 install with LAMP. I have been operating LAMP for around a year now without too much problem. However, My server does not appear to be letting port 80 requests from outside the network. Localhost and <my domain> works fine. Utilizing proxy.org or canyouseeme.org show blockage. What other diagnostics can I run to determine why requests are blocked?

My router is configured to pass port 80 requests TCP and I have a static IP. I purchased a business account with my ISP, therefore there is no potential for port 80 blocks from them. Also, I have allowed port 80 through on ufw as well.

Results from nmap:

mark@markserver:~$ nmap example.net

Starting Nmap 4.53 ( http://insecure.org ) at 2008-12-20 15:34 PST
Warning: Hostname example.net resolves to 2 IPs. Using 127.0.0.1.
Interesting ports on localhost (127.0.0.1):
Not shown: 1706 closed ports
PORT STATE SERVICE
80/tcp open http
139/tcp open netbios-ssn
445/tcp open microsoft-ds
631/tcp open ipp
902/tcp open iss-realsecure-sensor
3306/tcp open mysql
8009/tcp open ajp13
10000/tcp open snet-sensor-mgmt

Nmap done: 1 IP address (1 host up) scanned in 0.177 seconds

Results from netstat -tulpn

PID/Program name
tcp 0 0 0.0.0.0:902 0.0.0.0:* LISTEN 6474/vmware-authdla
tcp 0 0 127.0.0.1:3306 0.0.0.0:* LISTEN 5455/mysqld
tcp 0 0 0.0.0.0:139 0.0.0.0:* LISTEN 5590/smbd
tcp 0 0 0.0.0.0:8333 0.0.0.0:* LISTEN 7073/vmware-hostd
tcp 0 0 0.0.0.0:10000 0.0.0.0:* LISTEN 7233/perl
tcp 0 0 0.0.0.0:80 0.0.0.0:* LISTEN

Any suggestions?

[edited by: encyclo at 1:42 pm (utc) on Dec. 21, 2008]
[edit reason] exemplified, see terms of service [/edit]

buckminster1

3:21 am on Dec 22, 2008 (gmt 0)

5+ Year Member



SOLVED: My new business account (static ip) hardware required more configuration than I had completed. Additionally, I had place my new static ip in the VirtualHost directive in /sites-enabled/default instead of the wildcard '*.' I hate it when I do stupid things!