MacOS Server http(s) ports bound

apachehttplaunchdmacos

I've got a Mac mini 2014 (running macOS Sierra 10.12.2) with the Server.app installed.

I was planning on hosting a webserver on this device on the default http(s) ports. However, I've found that one of the services installed by the Server app has already bound these ports.

I've tried to disable the service that's binding these ports by using launchctl and stopping anything that vaguely looks like apache/httpd. Unfortunately, this wasn't enough.

Does anyone know which service is binding these ports?

Best Answer

Comment out listening ports at the beginning of the file /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf

Kill parent httpd process which contains substring "/usr/sbin/httpd -D FOREGROUND -f /Library/Server/Web/Config/Proxy/apache_serviceproxy.conf". For listing these running proceses use ps -fax | grep apache_serviceproxy.conf, for example.

Related Solutions

MacOS – Nginx on 10.7 with homebrew

If you type brew info nginx you should get answers to many of your questions. In particular, you should see something like:

To have launchd start nginx at login:
    ln -sfv /usr/local/opt/nginx/*.plist ~/Library/LaunchAgents
Then to load nginx now:
    launchctl load ~/Library/LaunchAgents/homebrew.mxcl.nginx.plist

So I expect if you link the plist to /Library/LaunchDaemons instead of ~/Library/LaunchAgents it will load at boot.

I don't know what you want to change, but it's the same nginx as you use on Debian, so you can copy over your Debian nginx.conf if you want. Also the brew package comes with a set of default/example configuration files installed under /usr/local/etc/nginx/.

The default conf runs on port 8080, so you have to edit it to run on port 80, and yes it will conflict with Apache running on port 80 so you have to turn Apache off or put it on another port. Apache config files are in /private/etc/apache2/ and you can turn it off via System Preferences -> Sharing -> Personal Web Sharing. (Note that this option has been removed in Mountain Lion. Mountain Lion still ships with Apache, but it is disabled by default.)

You can, of course, set it up however you want, but if you're looking for what's easy and Mac-like, just follow the Apache setup, which uses user and group _www and uses /Library/WebServer/Documents as document root and serves user content out of ~user/Sites.

MacOS – Mac OS X Server Mail services and Push Notifications to iOS devices

This problem was been resolved. The ASUS "Dark Knight" router which was providing the private LAN (NAT) and port forwarding to the Mac running OS X Server has a firmware bug. The bug manifest by DROPPING the ESTABLISHED TCP connection on port 2195 between the Mac running OS X Server and APNS, after two hours of quiescence. The router should not have dropped this connection, there was no firewall rule instructing it to do so. The lesson learned is to be much more selective and wise with regard to choosing routers (especially consumer off-the-shelf variety) for use with servers even for servers run in a small business context (like a Mac Mini Server).

Best Answer

Related Solutions

MacOS – Nginx on 10.7 with homebrew

MacOS – Mac OS X Server Mail services and Push Notifications to iOS devices

Heading

Related Question