Hello: This one is causing me to pull out what is left of my hair.... Ubuntu server 8.04 fully patched, running apache 2.2, mysql server, postfix mail server, and Hylafax (fax server), and ssh. I have installed but not configured: mysql, postfix, spamassin, clamAV postgrey. I am using DynDNS http redirects to my IP, and have port forwarding setup on my router. Everything was working fine for two months. Then, I needed to install a USB modem driver for my faxserver. To do that, I needed to update some kernel headers: linux-headers-2.6.24-19-server Then the modem requires a dgcmodem package. From http://www.linuxant.com/drivers/dgc/downloads-ubuntu-x86.php I download dgcmodem-7.68.00.12full_k2.6.24_19_server_ubuntu_i386.deb.zip The install worked ok, and the modem worked. Then I noticed that Apache stopped responding to External (WAN) side requests, but still serviced internal (LAN side) requests. I get 'Server taking too long to respond' as the message from Firefox... I suspect the modem driver install but can't say for certain b/c I did some other things that I can't recall at the moment...but I can't see how it would affect apache. I have been through every config file in Apache, host files, iptables, etc. and have found nothing abnormal/changed. A http request from any one of the 3 machines on my home LAN work - quick response. All necessary ports are open...nmap shows: Starting Nmap 4.53 ( http://insecure.org ) at 2008-12-03 11:08 EST Interesting ports on ubuntuserver.homeunix.com (192.168.0.110): Not shown: 1703 closed ports PORT STATE SERVICE 22/tcp open ssh 25/tcp open smtp 53/tcp open domain 80/tcp open http 110/tcp open pop3 139/tcp open netbios-ssn 143/tcp open imap 443/tcp open https 445/tcp open microsoft-ds 993/tcp open imaps 995/tcp open pop3s Nmap done: 1 IP address (1 host up) scanned in 0.303 seconds Traceroute gets to the server. ...So, this is driving me nuts...Please, any suggestions to help fix this??? Any tests/tools to run to help troubleshoot this? Thank you! John
After checking my router VERY carefully, the firewall was missing the entry to pass http requests on port 80 to my server IP address. All the other pass throughs were there. This is really very strange...how could a setting stored in persistent memory just go away?? I am a hardware EE and haven't ever seen anything like that... I know my Dlink router is long in the tooth, but this should never happen. Maybe a good time to get a new Linksys N for Christmas... -j