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

Search results

  1. D

    Resolved Backup fails since update to Plesk Obsidian 18.0.26: "Unable to validate the remote backup"

    Can you open such backups in Backup Manager and restore some data?
  2. D

    Forwarded to devs Backup Manager does not delete created backups

    Customer's backups are deleted in GUI on the page Also make sure a customer has permissions to manage his own backups: Backup and restoration of account data using the server storage Backup and restoration of account data using remote storage
  3. D

    Forwarded to devs An error occurred during the scheduled backup

    It looks like the file backup_xyz.de_2002120547.tar is empty and cannot be rotated automatically.
  4. D

    Forwarded to devs An error occurred during the scheduled backup

    Try to enable verbose logging in /usr/local/psa/admin/conf/panel.ini and in /usr/local/psa/admin/share/pmmcli/pmmcli-rc and try to find errors in - /var/log/plesk/panel.log - /var/log/plesk/PMM/migration.log
  5. D

    Forwarded to devs Incremental Backup: does not work quite as intended!

    These are known issues in Backup Manager that shall be fixed soon.
  6. D

    Unable to upload backup

    I cannot reproduce the issue in our environment. Could you provide the archive backup_info_2001280731_2002020231.xml.tar?
  7. D

    Forwarded to devs Incremental Backup: does not work quite as intended!

    It may occur once after upgrade to 18.0.23.
  8. D

    Issue Incremental Backup!!

    Could you provide here or in a private message listing of files from backup index files that you mean should not be included to incremental backups? The backup index files looks like /var/lib/psa/dumps/domains/example.tld/.discovered/backup_info_2001241746/cid_user-data and can be viewed via command
  9. D

    Issue Incremental Backup!!

    From which version of Plesk did you upgrade?
  10. D

    Forwarded to devs Not enough space to start backups even after changing the temporary directory to another disk

    Currently Plesk checks free disk space in DUMP_D directory and really uses it. I am not sure you need huge DUMP_TMP_D directory in Plesk 18.
  11. D

    Forwarded to devs Not enough space to start backups even after changing the temporary directory to another disk

    You can create multi-volume backups, in this case Plesk needs 2 x volume size free disk space. But you always need at least 1 x subscription size to restore data from backups.
  12. D

    Forwarded to devs Not enough space to start backups even after changing the temporary directory to another disk

    Plesk needs about 2 x subscription size free disk space in your case.
  13. D

    Forwarded to devs Not enough space to start backups even after changing the temporary directory to another disk

    You should change DUMP_D in /etc/psa/psa.conf too. It is main place where local backups are stored.
  14. D

    Forwarded to devs PleskBackup does not make incremental backups to S3 storage

    Strato said they fixed the issue. You can try to use HiDrive S3 again.
  15. D

    Forwarded to devs PleskBackup does not make incremental backups to S3 storage

    I am sorry Strato does not agree they have the bug and they do not provide any proof. The ticket number is 2019072401000031. You can try to contact them yourself.
  16. D

    Forwarded to devs PleskBackup does not make incremental backups to S3 storage

    It looks like there is a bug in HiDrive S3 API. When Plesk Backup Manager trying to get specified range of a backup file, e.g. 121151589-131637348 bytes, HiDrive S3 API returns different range ‭52428800‬-53477375 bytes that causes Plesk Backup Manager cannot find a base backup and creates a full...
  17. D

    Issue newbie asking for help with Backup import

    There are no neither migration.log nor pmmcli.log there.
  18. D

    Question plesk backup slow time to restore. "tar -z -f" use only one core

    man pigz I do not see way how restoration of big numbers of files can be speeded up significantly via using filesystem-based backups. The only possibility is creating raw dumps of block devices but it requires at least mount each webspace to its own partition.
  19. D

    Issue newbie asking for help with Backup import

    You need to go to Subscriptions > theatrum-vitae.com > Backup Manager to find out and restore your backup. Post the log files /var/log/plesk/PMM/migration.log, /var/log/plesk/PMM/pmmcli.log if you do not find your backup there.
  20. D

    Issue newbie asking for help with Backup import

    The backup was imported to /var/lib/psa/dumps/domains/theatrum-vitae.com. You need to create the subscription 'theatrum-vitae.com' and restore your data with the subscription's Backup manager.
Back
Top