SquirrelMac

Q: Disable Apache Yosemite Server

Hi,

 

Is there any way to disable Apache in Yosemite Server?

 

Have done this in previous version of OSX, but command doesn't run as the location has changed.

 

Any help would be greatly appreciated.

 

Thanks

Darren

OS X Yosemite (10.10.5), null

Posted on Sep 29, 2015 3:46 AM

Close

Q: Disable Apache Yosemite Server

  • All replies
  • Helpful answers

Page 1 Next
  • by Linc Davis,

    Linc Davis Linc Davis Sep 29, 2015 10:21 AM in response to SquirrelMac
    Level 10 (207,926 points)
    Applications
    Sep 29, 2015 10:21 AM in response to SquirrelMac

    What's wrong with turning off the Websites service?

  • by SquirrelMac,

    SquirrelMac SquirrelMac Sep 30, 2015 8:34 AM in response to Linc Davis
    Level 1 (5 points)
    Mac OS X
    Sep 30, 2015 8:34 AM in response to Linc Davis

    Despite the web services being off, the message i get from Rumpus is "another service is already running on the defined web port".

     

    Had this with our 10.8 server and removing apace, fixed this. But it doesn't look like it's possible with Yosemite?

  • by Linc Davis,

    Linc Davis Linc Davis Sep 30, 2015 8:06 PM in response to SquirrelMac
    Level 10 (207,926 points)
    Applications
    Sep 30, 2015 8:06 PM in response to SquirrelMac

    What other services are you running?

  • by SquirrelMac,

    SquirrelMac SquirrelMac Oct 1, 2015 2:52 AM in response to Linc Davis
    Level 1 (5 points)
    Mac OS X
    Oct 1, 2015 2:52 AM in response to Linc Davis

    Hi Linc,

     

    Apart from Open Directory (as this server is a replica), nothing.

  • by Linc Davis,

    Linc Davis Linc Davis Oct 1, 2015 6:33 AM in response to SquirrelMac
    Level 10 (207,926 points)
    Applications
    Oct 1, 2015 6:33 AM in response to SquirrelMac

    If you turn off OD, is the port still bound?

  • by SquirrelMac,

    SquirrelMac SquirrelMac Oct 1, 2015 6:34 AM in response to Linc Davis
    Level 1 (5 points)
    Mac OS X
    Oct 1, 2015 6:34 AM in response to Linc Davis

    Yes, still get the "welcome to OSX server" with Profile Manager, Xcode and Wiki.

  • by AlterDuo,

    AlterDuo AlterDuo Oct 1, 2015 7:12 AM in response to SquirrelMac
    Level 1 (0 points)
    Oct 1, 2015 7:12 AM in response to SquirrelMac

    I had a very similar experience.

     

    Under 10.10.4 and Server 4 if i rebooted the box all i had to do was kill Apache by Terminal Command (even with Web Services always off the OSX page overrode CrushFTP). This kept all the Settings functional like Port 443 for CalDav/CardDav while freeing up port 80 which served my CrushFTP Web Interface. Port 21 (without SSL) for FTP clients was also open by default.

    Apache killed with sudo launchctl unload -w /System/Library/LaunchDaemons/org.apache.httpd.plist

     

    Now under 10.11. and Server 5 odd things started to happen. After the first boot i noticed my CrushFTP Web Interface on port 80 was up and running. Everything seemed fine and i thought no more Apache Terminal killing (Web Services still off). Shortly after i noticed CalDav/CardDav not updating, in fact there was no communication at all on port 443.

     

    I realized that CrushFTP had an SSL setting activated even if i never used it on port 21. I disabled the optional SSL config and restarted my CrushFTP Server. CalDav/CardDaV started syncing right away BUT also the stupid OSX Server Page came back and was from that moment on absolutely persistent. Terminal command told me Apache unloaded and Web Services still off yet that **** page showed up.

     

    This also locked me out off my CrushFTP Admin Page so i could not even change that port to 8080 as a fallback.

     

    Anyways after a few hours of experimenting and smashing my head on the keyboard i activated Web Services out of curiosity and created a new page on port 80(!). This hilariously broke the proxy which seems to grab all connections now and i was able to reach my CrushFTP Admin Page where i swithced the port from 80 to 8080.

     

    Afterwards i deleted the new useless page in Web Services and modified the Standard OSX Server Page on Port 80 to redirect to my FTP Page on 8080. Not a pretty solution but so far the only way to kind of split services without completely messing everything up.

     

    Weirdly CalDav/CardDav stopped working again but were fixed with a quick On/Off Switch Flip in Server Admin.

     

    Something has clearly changed how connections are handled and sadly not in a good way so far. I hear from messed up Web Settings left and right.

  • by SquirrelMac,

    SquirrelMac SquirrelMac Oct 1, 2015 8:32 AM in response to AlterDuo
    Level 1 (5 points)
    Mac OS X
    Oct 1, 2015 8:32 AM in response to AlterDuo

    Hi Alterduo,

     

    That sudo command used to work in previous versions of osx, but not in Yosemite. (that i'm aware of any way)

    "Could not find specified service"

     

    Would be nice to get rid of that darn Apple webpage on port 80!

  • by AlterDuo,

    AlterDuo AlterDuo Oct 1, 2015 8:44 AM in response to SquirrelMac
    Level 1 (0 points)
    Oct 1, 2015 8:44 AM in response to SquirrelMac

    Yeah i tried a ton of other commands to effectively kill the internal OSX Apache but no luck. That page stays there like a rock. Seems certain ports are "reserved" now no matter what. Really unproductive that we are not able to change the OSX Server Page Standard Port.

     

    You could change the Rumpus Port to 8080 and redirect Port 80 there like i did but it is not my favorite solution so far.

  • by Linc Davis,

    Linc Davis Linc Davis Oct 1, 2015 10:34 AM in response to SquirrelMac
    Level 10 (207,926 points)
    Applications
    Oct 1, 2015 10:34 AM in response to SquirrelMac

    "Rumpus" seems to be a web and FTP server. You already have a web and FTP server. Why do you need "Rumpus?"

  • by MrHoffman,

    MrHoffman MrHoffman Oct 1, 2015 2:09 PM in response to SquirrelMac
    Level 6 (15,612 points)
    Mac OS X
    Oct 1, 2015 2:09 PM in response to SquirrelMac

    Okay, so you probably want to remove OS X Server and revert to OS X (make a complete backup of your environment — first!), so shut off everything and then drag Server.app to the trash, and then empty the trash.  That'll be the most supportable means for disabling everything that uses Apache on OS X Server.

     

    Alternatively and as Linc Davis mentions, Rumpus doesn't get you anything you don't already have — FTP is just as much of a massive hassle around modern networks and as wildly insecure and just as good at exposing your login credentials to any local Pineapple Wi-Fi or privileged network position, and that's whether you turn on FTP services in OS X Server or if you use an add-on.

  • by SquirrelMac,

    SquirrelMac SquirrelMac Oct 2, 2015 3:00 AM in response to Linc Davis
    Level 1 (5 points)
    Mac OS X
    Oct 2, 2015 3:00 AM in response to Linc Davis

    Here's the issue.

     

    I'm pretty loyal to Rumpus as it's been solid for many years. The Drop Ship feature in Rumpus is excellent.

     

    If i remove Server i won't be able to link to the OD.

     

    I think we might just go with a port number different to 80. Sadly Apple aren't doing us an favours these days.

  • by MrHoffman,

    MrHoffman MrHoffman Oct 2, 2015 4:33 AM in response to SquirrelMac
    Level 6 (15,612 points)
    Mac OS X
    Oct 2, 2015 4:33 AM in response to SquirrelMac

    FWIW and based on a quick look around (and you might already know this), what Rumpus calls "Drop Shipping", Apple calls "Mail Drop", and it's part of Mail.app in Yosemite and later, when you're using iCloud.

  • by SquirrelMac,

    SquirrelMac SquirrelMac Oct 2, 2015 4:43 AM in response to MrHoffman
    Level 1 (5 points)
    Mac OS X
    Oct 2, 2015 4:43 AM in response to MrHoffman

    Problem we have is we deal with the far east a lot. China block so much stuff that our other file transfer applications such as Dropbox, Wetransfer, Gdrive don't work for them.

     

    Dropship has always done the trick.

Page 1 Next