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

Upgrade Method - ssh vs control panel

bradz

Regular Pleskian
Hi, In the past, I have always used the Plesk Control Panel to run updates, however this last time, 9.5 to 10.2, it did not work and based on a post, I tried it using ssh which work! Is it safer or better to run updates using ssh? Pros or Cons?
Thanks!
Brad
 
For updating via interface make sure that you have not firewalled port 8447.
I think that more experienced Plesk users uses autoinstaller CLI command. I think that it allow to control upgrade process much more effectively.
 
I would never do it via the GUI; you can't see what went wrong when it breaks, which is half the time, and additionally, if you do it from command line, you can type:

Code:
export PLESK_QUOTACHECK_OFF=1

before running autoinstaller and that will prevent it from calculating the mailbox quota on every single mail account on the server, which can make the upgrade take hours longer if it's a big server.
 
Back
Top