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

bugs found 10.01

zeroday

Basic Pleskian
when migrating sites from server1 to server2
when in the httpdocs there is a .htaccess in some circumstances this is not being transferred, causing sites not not work properly. dunno what is reason, subfolders with .htaccess did work

imap folders are not being transferred during migration. Can be fixed by using imapsync, but you need to sync every exisiting mailbox (need to have username/password).

it is not stated very clearly that normally root access in ssh is not enabled and not possible, if you want to migrate, than root ssh login is necessary.

it is unclear why in normal circumstances CPU load on Apache gets >20% causing a lot of warning message, Plesk is not good utilized to make sure less mails are sent or why 20% CPU load is not ok, if it is not okay there must be suggestions why not.

further I was and am extremely happy that within 1.5 day I was able to migrate a whole server from 9.5 to 10.1 (old / new hardware)
 
if your apache load is above 20% then the machine is probably overloaded. apache is by far not the only thing needing cpu cycles. and 20% is too much. have a look at optimizing apache.

the limits preset in health monitor seem reasonable to me.
 
I Do not agree with you. I updated and checked the httpd.conf, and managed to change the memory usage behaviour severely, but that does not matter for the CPU load.
did not find any good direction for CPU load, only memory usage
 
That is a good tool, but than I must configure all my servers with server-status, being protected ..
that will cost some time..
 
Back
Top