I cannot get Mac OS X Server's web server to accept connections from other machines on the same LAN. This is on OS X 10.8.2, running on a Mac mini which originally shipped with Lion Server.
I can connect to it from the server itself, such as by going to
http://hostname.example.com in Safari.
Notice that connecting via the box's domain name works. This is because:
$ netstat -na | grep 80.*LISTEN tcp46 0 0 *.80 *.* LISTEN
That is, Apache is listening on all interfaces, not just
Disabling the firewall in the Security and Privacy settings pane doesn't change the symptom.
The firewall configuration looks harmless to me. (Dumped via
I'm certain the problem isn't on the client side. I've tried accessing it from:
- a month old iMac over GigE
- a 2 year old MacBook Pro over WiFi
- a 5 year old netbook running Ubuntu 12.04 over GigE and WiFi
This server is headless, and I do all my work on it from the iMac mentioned above, via both SSH and VNC. This means that while I am failing to connect to this server on TCP port 80, I am successfully using it on TCP ports 22 and 5900. This behavior is what caused me to start looking at the firewall configuration.
Here's what the network looks like:
The only reason there are two network switches because this network is spread over two rooms. With a switch in each room, there can be just one cable going between them. I ruled out the managed switch as the problem source with the WiFi test. I exonerated the dumb switch by temporarily running a long cable from the server to the managed switch.
The cable modem and the WiFi router (an AirPort Extreme) each have 4-port switches built in, but only one port on each is used, so no traffic goes through them that doesn't absolutely have to. The DHCP and caching DNS servers are turned off on both routers, since those duties are being done (successfully!) by the server in question. The AirPort is in bridging-only mode.
And yes, I've rebooted the server. And the clients. And the routers. And the switches. :)
My best guess is that the problem stems from having upgraded this box from Lion Server. If so, a complete reinstall will fix this, but that goes against all of my Unix server management training. I want to fix this server in place, if I can.