• Our team is looking to connect with folks who use email services provided by Plesk, or a premium service. If you'd like to be part of the discovery process and share your experiences, we invite you to complete this short screening survey. If your responses match the persona we are looking for, you'll receive a link to schedule a call at your convenience. We look forward to hearing from you!
  • The BIND DNS server has already been deprecated and removed from Plesk for Windows.
    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. We strongly recommend transitioning to Microsoft DNS within the next 6 weeks, before the Plesk 18.0.70 release.
  • The Horde component is removed from Plesk Installer. We recommend switching to another webmail software supported in Plesk.

Server Reboot Capability

J

Jericon

Guest
I am working on setting up a cluster of customer servers running Plesk. We are going to need to give our end users the ability to reboot their servers and we also need to have our own access to the admin login for entering it into Plesk Expand.

So the issue is this. If we give the end user Admin access, they can change the password and cause issues with Plesk Expand. However, if we only give them client access, there is no way for them to reboot the server.

Does anyone have any ideas how to get around this? Perhaps adding a secondary admin user for the customer, or add the ability to reboot from a client level.

Thanks in advance!
 
How do I set up an auto reboot on a server?

Start the Task Scheduler.

Under Windows 2000/XP this is located in Start Menu > Programs > Accessories > System Tools.

Check that the Task Scheduler is running.
You may do this by checking the Advances menu and seeing if it lists 'Stop Using Task Scheduler'. If it is listed, this means the Task Scheduler is running. If it says 'Start Using Task Scheduler' then the Task Scheduler is not running. Click on the option to start it.
 
We are not looking for automatic reboot capability. That's easy enough to setup. We are looking for the ability to grant a client the 'reboot server' button in the Plesk Console. If that is not possible, then some way to grant a secondary admin account to a server.
 
If we give the end user Admin access, they can change the password and cause issues with Plesk Expand. However, if we only give them client access, there is no way for them to reboot the server.

Not all problems need a technical solution. Can't you just tell them that they shouldn't change Plesk's admin password without your knowledge or there'll be trouble?

You could also disable the password change button, but of course it can be added again by anyone logged in as admin.
 
This is what sudo was made for. Give them a regular unprivileged shell account, and let them use sudo. In the sudoers file just setup the commands (/sbin/reboot) they are allowed to run and the unprivileged shell account.
 
Back
Top