Linux - ServerThis forum is for the discussion of Linux Software used in a server related context.
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.
Why can't I access my web server from another machine on the local network.
I've changed the httpd.conf to allow access from the network to port 80; but still no access. Interestingly though, I can access the webserver:631 (cups) as well as any other port (for example an alfresco install on port 8080), but not the default port 80.
OK, thanks. It seems as if my iptables does not allow port 80. But according to firewall-config on the "services" tab, it looks like port 80 is indeed open?
Looks like the port 80/tcp is open already. Perhaps you need to delete the 2 occurrence of the iptalbes rule (and the 80/udp)
I don't use Fedora, so better read the official documentation of firewalld
For quick instructions check this
Add the --permanent option to persist over restarts.
Once the port is open in firewalld, you do need something listening on port 80, usually the httpd server.
And maybe you need to expound on the "I can't access" problem. Maybe the "webserver" listening on port 80 is not booted up? Or maybe it's up and firewalld allows connection but SELinux doesn't allow it?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.