Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Redhat v8.0 (soon to be Fedora? or maybe I will just go back to Slackware)
Posts: 857
Rep:
Apache won't answer on Port 80, but will on 443
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.
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?
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.