"Error: no secure shell available" fixed!
Hi guys,
just for the records, I found what the problem was with this one. Plesk 10 has, in the set of permissions, something that says:
"Setup of potentially insecure web scripting options that override provider's policy" (btw, I really have no idea what this text really means, the documentation is very scarce here). This permission / feature / whatever can be enabled / disabled per reseller, per service plan and per subscription. If the option is unchecked (which is the default), basic Plesk functionality will become simply unavailable if logged in as non-admin, such as:
- create a subscription
- change the ftp account password
- deploy applications (e.g. Wordpress)
As soon as I ticked that box ("Setup of potentially..."), I was able to do all the above.
The "Error: no secure shell available" message has *nothing* to do with "Management of access to the server over SSH" setting, because, with or without the latter one enabled, I still kept getting this error.
This "Setup of potentially insecure blabla" is a feature which, obviously, was never tested in the Parallels QA labs, because having this unchecked clashes basically with the some essential functionality Plesk is supposed to provide, like the above mentioned ones, and which is achieved by executing scripts which are not allowed in the default configuration, how clever is THAT? If this feature was tested as a non-admin, this bug would have been so obvious from the very beginning.
I don't even know if Plesk product management team had a clear idea about what they wanted to achieve with this in the very beginning, just as I believe the developers didn't know exactly what they had to do once they started to write the code.
It's that, sometimes, these bugs turn out to be in fact bad design decisions, based on unclear specifications.
Have an excellent day,
Adi
Facebook
Twitter
