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

Issue Backup issues after updating to 18.0.51 - Unable to validate the remote backup

hamstercodes

New Pleskian
Server operating system version
Ubuntu 20.04.6 LTS
Plesk version and microupdate number
18.0.51
After updating to 18.0.51 I started getting random warnings from my scheduled backup tasks.
This only happens to a couple of my customers and even for them a couple times a week (not every day).
I get a warning saying "Unable to validate the remote backup. It may not be restored. Error: Unable to extract dump header"

I'm using OneDrive as my remote location. I tried unchecking "Validate backups via checksum" but that didn't stop the warnings.
I'm using Backup to Cloud Pro extension.
 
Backups were not modified on the past version iterations. The error message rather points to long (too long) response times of the backup target that are causing timeouts.
 
Backups were not modified on the past version iterations. The error message rather points to long (too long) response times of the backup target that are causing timeouts.
Maybe the error message could be closer to what actually happens? Now it seems to suggest there is something wrong with the file itself.
 
I'm still having this issue. Haven't really had time to debug more. Tried splitting the backups into smaller files as well but no luck
 
I've been having the same issue for at least three weeks. I'm backing up to a Google Cloud Storage bucket (S3-compatible), so I don't think that's the problem.
 
I had something like that some Updates ago. It caused issues when bachup. I identified two issues, one was trouble with 2 htaccess files. I removed them, waited some time and got up one which works (there must have been a fault somewhere in the files). The second was a problem that 3 IP's where not connected as they sould. I disconnected the IP, connected the IP's at the server via ssh again, reread in plesk and reconnect them. Last issue at one domain I wasn't able to solve, so I deleated the domain out of plesk. After that next backup went through as normal.
 
Back
Top