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

Issue Smart Update - Fails on large WP Site

Vorden

New Pleskian
Server operating system version
Debian 11.5
Plesk version and microupdate number
Plesk Obsidian v18.0.47_build1800221003.04 os_Debian 11.0
The Smart Update has been failing for many issues, most we have resolved. It is now giving the following error:

Request to backend API failed with error: Request failed with status code 500

Prior to this it was timing out so we increased the limit.

WP site size is 160GB - Free Disk Space is over 1TB SSD

it gets to 40% and stalls

smart-update.png

Any advice will help.
 
The Smart Update has been failing for many issues, most we have resolved. It is now giving the following error:

Request to backend API failed with error: Request failed with status code 500

Prior to this it was timing out so we increased the limit.

WP site size is 160GB - Free Disk Space is over 1TB SSD

it gets to 40% and stalls

View attachment 21696

Any advice will help.
Hi,
WPT is able to properly clone (create a test site) such big WordPress sites. There is one known issue with cloning when the site contains a lot of small files (bug ID EXTWPTOOLK-9454), if this is your case, then you should see the error "WordPress site was cloned with errors: Task is not responding".

If you see different error, could you please check the panel.log for the stack trace or something like that and post it here? (please remove all sensitive information, e.g. domain name, site name and etc. Also you can send that info directly to me via private message)
 
Thanks for the reply. I have decided not to use the Smart Update in this case as the size of the site is too large. It would be nice if it would be excluded the upload folder in the test site. For now, I am making a backup of the Theme folder / plugins folder and the database. I then perform the updates and check manually.

V
 
Back
Top