- Plesk for Linux
Note: This article has the reference to the issue with the fix available:
- #EXTWPTOOLK-2723 "Smart Update procedure is now more patient, so it has much less chance to fail because of a timeout."
- WordPress Toolkit 4.1.0 30 May 2019
When using Smart Updates the following error is shown:
PLESK_ERROR: Could not update the WordPress instance. If you enabled Smart Update on a website that supports HTTPS, secure the website with a valid SSL/TLS certificate from a trusted certificate authority to get Smart Update to work.
The next errors can be found in the
/var/log/plesk/panel.logfile with enabled debug logging:
CONFIG_TEXT: ERR [extension/wp-toolkit] Failed to catch the initial state of the cloned instance.
Details: [AI I#100] Failed to perform visual comparision of instance #100: action #1309635 not finished withing 600 seconds
CONFIG_TEXT: ERR [extension/wp-toolkit] Failed to compare the initial state of the cloned instance and it's updated version. Details: [AI I#125] Failed to perform visual comparision of instance #125: action #1342037 not finished withing 600 seconds
DEBUG [extension/wp-toolkit] [AI I#125] Failed to perform visual comparision of instance #125: action #1342037 not finished withing 600 seconds
It is WordPress Toolkit bug #EXTWPTOOLK-2723 which is going to be fixed in future product updates.
As a workaround, perform the next actions:
Connect to the server via SSH.
Create a backup of the
# cp -p /usr/local/psa/admin/conf/panel.ini /usr/local/psa/admin/conf/panel.ini.back
/usr/local/psa/admin/conf/panel.inifile via any text editor and add the next rows to the end of the file:
visualComparisonPollInterval = 360
visualComparisonPollAttempts = 5
If the issue still occurs increase the timeout evenmore:
CONFIG_TEXT: visualComparisonPollInterval = 360
visualComparisonPollAttempts = 10