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

    Forwarded to devs 300s loop when access Backup Manager IF

    You can decrease connection timeout via an option in the panel.ini file [pmm] ftpConnectionTimeout = 30
  2. D

    Forwarded to devs Remote FTP backups for a particular domain show in backup list of other domains

    Could you explain the case you provide your own FTP storage to your customers? May be ability to share remote server backups (as local backups) helps you.
  3. D

    Forwarded to devs Remote FTP backups for a particular domain show in backup list of other domains

    Remote backups are personal and should be configured to be created at different places under different accounts.
  4. D

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

    This is correct, remote backups are larger because they contains additional metadata (signs, headers, indexes ...).
  5. D

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

    No, it is not.
  6. D

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

    I cannot reproduce the issue neither Strato's HiDrive nor Dropbox. Try to check your routes via mtr command
  7. D

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

    I'll try to test Strato HiDrive.
  8. D

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

    No, it is not possible. We have added validation of remote backups in 18.0.26 to make sure you can restore your data when it is required.
  9. D

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

    We have added option to /usr/local/psa/admin/conf/panel.ini to limit maximum TLS version The option will be available since Plesk 18.0.27
  10. D

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

    I have reproduced the issue with Hetzner's storage box but it looks like the issue is on Hetzner's side because of it is reproduced via curl command too. I tried to upload a test file about 2 MB size and got the following error Also size of the file uploaded 1753088 bytes was not equal...
  11. D

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

    I'll try to use Hetzner's storage box.
  12. D

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

    Make sure your scheduled backups do not rewrite each other (may be from different servers). Also check you have not duplicate records in BackupsScheduled table.
  13. D

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

    Can you open in Backup Manager backups created before Plesk update? And what was previous version of Plesk?
  14. D

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

    I cannot reproduce the issue. In general I can recommend to use pure FTP servers (not proxy for cloud storages because they are often not fully compatible with pure FTP servers) or submit a request to Plesk support.
  15. D

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

    It is not error. When Backup Manager opens a backup it gets its size and then read 1 MB of data from the end. You need to looking for lines with 'Curl error' strings.
  16. D

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

    Are there text like 'Trying to resume upload'?
  17. D

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

    There was issue PPPM-11825 in Plesk Obsidian < 18.0.26. If workarounds above do not help I recommend 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/PMM/backup-<date_time>/backup.log...
  18. D

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

    Try to use the option ftpForbidReuseConnection in /usr/local/psa/admin/conf/panel.ini
  19. D

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

    Try to use passive mode on page Backup Manager > Remote Storage Settings > FTP(S) Storage Settings.
  20. D

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

    In general I recommend to use another FTP storage or one of cloud storages (Amazon S3, Google Drive, OneDrive, Dropbox) to avoid such errors.
Back
Top