Apache won't answer on Port 80, but will on 443

KevinJ · 02-03-2003, 05:05 PM

I don't know what happened, but my Apache server just quit answering on port 80. If I use an "https://" instead, then it works. That means port 443 is working right?

I don't have any fancy firewalls, I don't have anything restricted in my hosts.deny

Nothing is being logged in /var/log/messages, /var/log/secure, or /var/log/httpd/access_log

An nmap scan of my ip addy shows that its listening on port 80. A local "links" connection works fine.

KevinJ

DavidPhillips · 02-03-2003, 05:07 PM

try it by ip address. It sounds like a dns or virtual host problem

KevinJ · 02-03-2003, 05:13 PM

I am trying the ip address... there is no FQDN on this server.

-K.

KevinJ · 02-03-2003, 05:35 PM

Any other ideas?

bulliver · 02-03-2003, 05:46 PM

Are you sure you didn't accidently erase or comment out something relevant in http.conf? Look for...

Code:

# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
#
Port 80

If that looks fine then what happens if you specifically bind apache to your ip and port? ie:

Code:

# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#
#Listen 3000
#Listen 12.34.56.78:80

Do you have something messed up in your virtual host section?

KevinJ · 02-03-2003, 05:57 PM

my sections of code look exactly like yours. I don't have anything special in the virutal host section. just the defaults as far as I can tell.

-Kevin

KevinJ · 02-03-2003, 06:33 PM

I replaced my /etc/httpd/conf/httpd.conf with the default one from the apache installation files and restarted my httpd daemon.

Its still doing it. Perhaps it has something to do with trying to access it from work or something?

Can someone else try to get to http://24.55.121.45 and see if they can at least get the default Apache front page?

-KevinJ

bulliver · 02-03-2003, 06:54 PM

"An error occured while loading http://24.55.121.45:
Could not connect to host 24.55.121.45"
sorry...

I can ping you fine.

DavidPhillips · 02-03-2003, 07:16 PM

Your isp may be blocking port 80 so you cannot run a server

you can set it up for another port and try it

try http://localhost on the server, if it works it's probably your isp.

If you have a local network try it there.

KevinJ · 02-04-2003, 10:51 AM

Well.. it works from the local network, but won't from outside... it does look like my ISP is blocking port 80, but I don't see why they would.

Wouldn't it make more sense for them to block things at the packet level instead of the port?

Thanks for the help,

Kevin

DavidPhillips · 02-04-2003, 08:10 PM

A lot of them have started doing that. They will not filter packets due to the cpu requirements. It is very easy for them to close all incoming traffic on port 80, and it is effective.