• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Not happy at all

W

Wolfman97

Guest
It is a long story of really terrible technical support, but I was recently forced to buy Plesk for my server by godaddy.com.

I will not bore you with the list of unnecessary configuration issues that raised, nor the tale of how my server had to get wiped out and be down for three days while it was installed.

I will only tell you about the current problem. Currently, Plesk randomly decides that certain directories don't have permissions to be viewed through the web. No rhyme or reason. Nothing else going on that should affect it at all. It just picks a few directories and decides no one can see them anymore.

I have found that there are only two corrections to the problem. One is to delete the directory entirely and replace it. That cures the problem, at least partially. The other option is to go through Plesk and one-by-one pick the files and set the permissions on them. I have about ten thousand files so you can probably imagine the charming things I am saying about your software at the time.

OK, so I didn't want it but I was forced to buy it -- and pay for it. I would uninstall it but then I would be back to cleaning off the disk and starting over again -- my web site would be down again.

So let's just see if we can do something easy. Can one of your tech support people tell me why it is randomly locking down directories? And how can I stop it?
 
I should add. There is nothing special about the directories that get locked down. They don't contain any different content, and they were all created the same way. Some of the ones that are locked down are directories where we already went through and individually set the permissions on hundreds of files.

Your software apparently only does these permissions one file at a time, so this routine gets old pretty quickly. when it happens again for no apparent reason, it gets really, really old.
 
Back
Top