How to Stop Apache on macOS

When you disable Web services in OS X Server, it may seem like the Apache server is still running because there are other server functions that use HTTP as a basis for service. This can lead to confusion when trying to run Rumpus, another web server software, on your Mac.

The reason why OS X Server leaves Apache on is because it needs to respond with a message saying 'Web service is off' when you try to access the Web service. For this reason, OS X Server blocks Rumpus even though it's not doing anything, effectively preventing it from running.

To resolve this issue, you can turn off the Web service in OS X Server. This may seem daunting, but it's a better option if you don't need OS X Server's Web service. By turning it off, you'll simplify access and minimize client firewall problems.

In Rumpus, you can specify the Web server port on the 'Web Settings' window, 'Options' tab, and the secure Web port on the 'Network Settings' window, 'Secure Services' tab. If you need to run both Rumpus and OS X Server Web services, you can run one service on the primary Web port (80) and another on an alternate (like 8000).

Rumpus includes its own HTTP and FTP server engines, which are totally separate from the Web and FTP servers built into the system. This means they coexist very well, so there's no conflict.

In general, Rumpus and OS X Server get along great. However, if you're experiencing port conflicts when trying to run both services, it may be necessary to configure them to use different ports.

It's worth noting that this information applies to OS X Server 4 and earlier. For those using OS X Server 5 or later, an updated blog post provides further guidance on how to handle this issue.

Macos apache stop