• 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.

Issue "Updates & Upgrades" without root enabled

bmit

New Pleskian
Hi All,

An interesting scenario, although I'm sure many have come across.

So for security purposes we have disabled the root account.

Now to Manage Plesk we use the "admin" account, however a slight issue I've come across is:

When wanting to use the "Updates & Upgrades" feature on Plesk (i.e to install components & updates), it prompts you to login (new install, first time loading it). It will not let you use the "admin" account as this account doesn't exist in the Linux OS. It attempts to use the "root" account (We disable this). How can we get around this?

Also to note, we've just built this Linux Plesk VM within Azure, I will be happy to document the process and findings (there has been a couple of issues which I've managed to resolve).

Thanks all,

Sam
 
Some of the important internal processes inside Plesk should be run under root account. Therefore disabling root account on Plesk server is not good idea.
 
Back
Top