Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
The APS Catalog has been deprecated and removed from all Plesk Obsidian versions. Applications already installed from the APS Catalog will continue working. However, Plesk will no longer provide support for APS applications.
Please be aware: with the Plesk Obsidian 18.0.78 release, the support for the ngx_pagespeed.so module will be deprecated and removed from the sw-nginx package.
Hello!
Sory for late reply.
It seems that you use FTP repository for backup files placing. If so you can try to download main backup archive <HOSTNAME>_full-_<DOMAIN.TLD>_vhost_1307282008.tgz on your local computer via plesk UI interface. During downloading it collected into original archive...
hello!
Sorry for late reply. You can restore only one domain from full server backup.
To make it you should create domain with requested name (if it's not exist). then go to Subscriptions->/name/->Websites and Domains->Backup manager
If you choose backup file from this repository it will restore...
Hello!
Could you please to share config of your ftp repository. You can sent it me in private message. It can help us to reproduce and understand root cause of described issue.
Guys, backup encryption feature encrypts only passwords inside your backup xml files. Password phrase is requested during restore to decrypt all passwords inside xml files.
Hello! It seems that you have upgrade of mysql server but tables were not upgraded. Try to make mysqlcheck and mysql_upgrade of you databases to fix this inconsistency.
Hello!
I don't see any errors in log you attached here.
Check of the next files will be more useful for detailed info:
/usr/local/psa/sessions/<timestamp>/migration.result
/usr/local/psa/sessions/<timestamp>/stderr
/usr/local/psa/sessions/<timestamp>/psadump.log
Thank you, it's the known issue and will be fixed at one of the future MUs. now we can't backup files owned by apache correctly.
As a workaround I can suggest you to change owner of this content using next scheme:
0770 apache:apache ==>> 0770 sysuser:apache
and then perform backup task again.