neonsox

Q: Permissions issue in Server - FTP

Hello,

 

Yesterday, I thought it would be a good idea to move OS X Server (El Cap) from Applications to Utilities, just to be organized and so on. Bad idea. Whatever I did hosed permissions and my FTP user can no longer write to a designated folder. For whatever reason, I can't set permissions within server to the folder. "OK" is never an option. I'm logged in as the user who should be the owner of the folder since it lives under Pictures, so while I can set permissions outside of Server in Finder just fine, Server won't let me set permissions within that user's folders. Other users and their folders - yes - even when Finder tells me I have no rights.

 

Something got housed when I tried to move Server. Since then, I've tried to revert to a Time Machine backup, reinstall Server, etc. I even disabled System Integrity protection (turned it back on). If I log in as an Admin, I still can't set permissions from within Server on that folder. Really weird.

 

Anybody else ever experienced this? What's the big deal with moving Server anyway? Thanks in advance.

MacBook Pro (13-inch Early 2011), OS X Mountain Lion (10.8.2)

Posted on Jun 30, 2016 7:04 AM

Close

Q: Permissions issue in Server - FTP

  • All replies
  • Helpful answers

  • by cdhw,

    cdhw cdhw Jul 1, 2016 6:11 PM in response to neonsox
    Level 4 (2,623 points)
    Servers Enterprise
    Jul 1, 2016 6:11 PM in response to neonsox

    Server.app contains a large number of files and libraries that need to be in a specific place, i.e. /Applications/Server.app/...

     

    Trying moving Server.app to the Trash then re-download it from the App Store.

     

    C.

  • by neonsox,

    neonsox neonsox Jul 6, 2016 11:18 AM in response to cdhw
    Level 2 (209 points)
    Servers Enterprise
    Jul 6, 2016 11:18 AM in response to cdhw

    I did that, didn't help. I did find that deleting the configuration files in \Library\Server\FTP allowed me to set permissions again (OK was lit up).

     

    Testing this manually on the same machine, it works. I can log in, read, write, everything from the command line. I haven't tested from another machine on the network. But there's no firewall in place (internally), didn't enable the adaptive firewall. It worked before, so it's perplexing.