• The new Python extension is now available. It allows customers to deploy and manage WSGI-based Python applications on their websites directly from Plesk.
  • The Plesk Mobile apps for iOS and Android and the Plesk Mobile Center extension have been deprecated, and are no longer available for new installations. In Plesk Obsidian 18.0.84, the Plesk Mobile Center extension will be removed from servers during the upgrade, and the Plesk Mobile apps will lose their server management features.
  • The Social Login extension has been deprecated and will be removed in Plesk Obsidian 18.0.84. After that, it will no longer be possible to log in to Plesk with a Google, Facebook, GitHub account, or with a passkey. Plesk usernames and passwords, as well as logging in with a WebPros Account, are not affected.

Question Message after reinstalling a backup 2 days before

alpinecare

New Pleskian
Server operating system version
Debian 10.13
Plesk version and microupdate number
18.0.53
Hello everyone,

following a big problem on my PrestaShop 1.7.8, with "creative element", I no longer had a home page, just a phrase "popular products"
For this reason I went back with the backup manager and put back 48 hours.

The problem comes back on my PrestaShop despite going back (I had no problems 48 hours before)
and I noticed this message at the end of the backup,

Restoring task details July 29, 2023 8:45 PM

Restore from backup July 25, 2023 03:39 is complete, although some issues have occurred.


Warning: Restore domain "domain.com"
Failed to restore the extension composer: Utility returns not valid response: <html> <head><title>504 Gateway Time-out</title></head> <body> <center><h1>504 Gateway Time-out</h1></center> <hr><center>nginx</center> </body> </html>

is this a bug or another configuration problem on Plesk? Thank you in advance for your precious help.

Stephanie
 
@alpinecare, for the restore issue: You can try some tweaks that might solve the issue.

# vi /etc/sw-cp-server/config

1) Increase the client_max_body_size to several GB, for example
client_max_body_size 4096m;

2) Increase the value of "fastcgi_read_timeout" and "fastcgi_send_timeout" to something long like 1200 seconds or even longer:
fastcgi_read_timeout 1200;
fastcgi_send_timeout 1200;

Save these changes to sw-cp-server/config, then edit /usr/local/psa/admin/conf/php.ini to allow a longer execution time, for example:
max_execution_time 1200

Save the changes to /usr/local/psa/admin/conf/php.ini.
Then restart the panel services:
as root service sw-cp-server restart && service sw-engine restart

For the Prestashop issue: That is an issue of Prestashop, not Plesk.
 
Back
Top