• 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!
  • We are looking for U.S.-based freelancer or agency working with SEO or WordPress for a quick 30-min interviews to gather feedback on XOVI, a successful German SEO tool we’re looking to launch in the U.S.
    If you qualify and participate, you’ll receive a $30 Amazon gift card as a thank-you. Please apply here. Thanks for helping shape a better SEO product for agencies!
  • 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.

Input Very Slow Advisor - Plesk Update time out

Daniel Richards

New Pleskian
In recent days we've come across a new issue involving painfully slow Plesk Advisor, and an inability to use the Plesk Update function. We have found the trigger for this behaviour, which doesn't appear to be documented yet by Plesk.

This is on Plesk Onyx 17.8 update 38 on dedicated servers in OVH data centres

We looked at this article:
Plesk Installer and Advisor extension are working slow
and this is not relevant to the issue we face - there is no problem with nameserver resolution speed, and the query
Code:
/usr/local/psa/admin/bin/php -f '/usr/local/psa/admin/plib/api-cli/settings.php' -- '-g' 'password_strength'
returns in 0.0102 seconds, so well below the 1 second the article is looking for.

We have eventually traced the issue back to OVH and their DDOS mitigation service. We had set the DDOS mitigation provided by OVH to 'Permanent' as opposed to the default of 'automatic' It is meant to only add an extra 30-50ms to each query as they get analysed under their DDOS protection system, and for this particular usecase - we thought we would benefit from this being permenantly active instead of risking a delay following a DDOS attack while the automated system kicks in. It's not meant or expected to cause any other problems other than a 30-50ms delay on each query.
The problem with Plesk Advisor is resolved when the OVH DDOS protection system is restored to 'automatic' and therefore inactive unless it detects an attack underway.

We don't yet understand why this occurs as other aspects of the server, including network throughtput work just as expected. The only issue we can find between plesk and OVH DDOS protection system seems to be with advisor and update/upgrade in plesk.

We have found the same now on an unrelated plesk 17.8 setup on a different OVH server in a different datacentre in a different region, so this is unlikley to be an isolated problem for Plesk and OVH customers if DDOS mitigation is active.

I wanted to put this here, so if anyone else with this issue uses OVH servers- they can see this extra potential cause to consider - so hopefully avoid the many hours that has gone into tracking this issue this far.
 
Back
Top