• Hi, Pleskians! We are running a UX testing of our upcoming product intended for server management and monitoring.
    We would like to invite you to have a call with us and have some fun checking our prototype. The agenda is pretty simple - we bring new design and some scenarios that you need to walk through and succeed. We will be watching and taking insights for further development of the design.
    If you would like to participate, please use this link to book a meeting. We will sent the link to the clickable prototype at the meeting.
  • Our UX team believes in the in the power of direct feedback and would like to invite you to participate in interviews, tests, and surveys.
    To stay in the loop and never miss an opportunity to share your thoughts, please subscribe to our UX research program. If you were previously part of the Plesk UX research program, please re-subscribe to continue receiving our invitations.
  • The Horde webmail has been deprecated. Its complete removal is scheduled for April 2025. For details and recommended actions, see the Feature and Deprecation Plan.

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