I am unable to backup after upgrading to latest version.
I deleted and reinstalled the plugin but am still getting the same error message:
The HTTP response test get an error "Operation timed out after 15000 milliseconds with 0 bytes received"
when I try to run my backup jobs (I have 2).
The backup was working previously.
Many thanks
Jacqueline
Updated plugin to version 3.1.3.
Got the same as well with message in WP admin - "ERROR: Step aborted: too many attempts!"
Standout Error seemed to be this - "ERROR: Dropbox API: (401) Access token not found."
Solution for Backup to Dropbox...
Use Tar GZip.
Delete Dropbox access code and re-authenticate with full access.
Run backup.
Worked fine on all nine sites I administer.
Same here. Error log is like this:
1. Try to send backup file to Dropbox …
[13-Kas-2014 08:15:41] ERROR: Dropbox API: (401) Access token not found.
[13-Kas-2014 08:15:41] 2. Try to send backup file to Dropbox …
[13-Kas-2014 08:15:42] ERROR: Dropbox API: (401) Access token not found.
[13-Kas-2014 08:15:42] 3. Try to send backup file to Dropbox …
[13-Kas-2014 08:15:43] ERROR: Dropbox API: (401) Access token not found.
[13-Kas-2014 08:15:43] ERROR: Step aborted: too many attempts!
[13-Kas-2014 08:15:43] ERROR: Job has ended with errors in 18 seconds. You must resolve the errors for correct execution.
I've reverted back to the previous version and it's working properly again. If others also want to revert, this is the link: https://downloads.wordpress.org/plugin/backwpup.3.1.2.zip
I'm really tired of developers rolling updates without properly testing. This has happened to me too much recently, I'm using at least 5 old versions of other plugins because new versions are broken. Don't change something if it's not broke!
Thanks for the answer - I am trying to backup to a directory, on the web server and have tried email but it fails with both methods.
Hello alexanghel,
please try to update there are many spped improvmends for using Zip Archives in.
Moderator: Please add a warning to the software, and (if you can) to this forum:
"Don't publish your actual folder path, database name, user name, table prefix on any public forum"
Plugin Author: Make a link on the job status screen "Job Status Without Account Info, For Posting", or even better, default to redacted with a link "version with Full path and account information".
alexanghel and markarnold, you just gave every hacker in the world all they need to exploit any holes in your hosting account's security, except your password. And most people use passwords that are broken within a few thousand attempts.
markarnold, you also posted your S3 account information, your account name is in that full path, isn't it?
Hi,
updated to 3.1.3 and the error is
FEHLER: Dropbox-API: (401) Access token not found.
Thanks gezginrocker for the link to the old version ;-)
markarnold and alexanghel:
does the temp folder exist? You may have to create it yourself, in FTP. Do you have permission to write there?
alexanghel, your /var/www/... folder is very likely wrong. No user files should be accessing /var/ in normal server setups. Try checking your FTP settings, or your CPanel error log, or your technical support people, to get the full path to a valid folder.
You really shouldn't ever be storing backups in the web-accessible part of your account. Make (ask your tech support for help if needed) a folder above the www/ (or public_html/) folder, for your backup. Shorter folder name, and much harder for hackers to steal your backup.
For the Dropbox problem please make a ne authentication with dropbox. I have updated to oAuth2 and normely the update shuold work automaticliy, but it looks like it will sometimes fail.
I'm having an issue with a site I just transferred to a new domain. Backups uploaded to my AWS S3 bucket with no problems on the old domain. I'll try to be as detailed as I can.
The new domain is in the same general environment, same hosting account, but a different addon domain. Before the wordpress installation was at domain.com and now it is at another-domain.com/folder/. The server path changed from .../public_html/domain.com/ to .../public_html/another-domain.com/content/.
To keep things simple, I'm backing up the database by itself, and the backups are only 1-2MB and only takes about 15 seconds to complete. The backup seems to be created, it connects to the S3 bucket, checks for "not aborted multipart Uploads" and then shows the error message. Here is a snippet from the log:
1. Trying to send backup file to S3 Service …
Connected to S3 Bucket "backups" in
Checking for not aborted multipart Uploads …
ERROR: S3 Service API: Validation errors: [Prefix] must be of type string
It tries three times and fails each time. If I turn off multipart upload, then it works fine. It worked before with multipart upload and I think this is better for the files backups, which are a lot bigger (~70MB).
The files backup takes longer, and I have Reduce server load set to maximum, and (I can't find where the setting was) it is set to restart on each step, so it takes 600-800 seconds. Maximum script execution time is set to 300 seconds, and after that it says "Restart after 298 seconds." and keeps going.
What could be the cause of the multipart upload problem?
I have been using previous versions for BackWPup to a Zip Archive, transferred to Dropbox without problem.
With the upgrade to the latest version 3.1.3 of BackWPup, now getting the error:-
[16-Nov-2014 12:05:50] 1. Trying to create backup archive …
[16-Nov-2014 12:05:50] Compressing files as ZipArchive. Please be patient, this may take a moment.
[16-Nov-2014 12:05:50] ERROR: ZipArchive returns status: Entry has been deleted
[16-Nov-2014 12:05:55] Backup archive created.
[16-Nov-2014 12:05:55] Archive size is 21.02 MB.
[16-Nov-2014 12:05:55] 3645 Files with 48.18 MB in Archive.
In spite of this, the archive does appear to be created with the right files in it, but the process is recorded as an error and sends the error email.
I see that this has also happened with previous versions and one recommendation is to go to tar.gz archives. I have done this, and don't get the errors any more, but I get duplicates of the following 2 files within the archive:-
backwpup_readme.txt (different dates, same size 512 bytes)
manifest.json (different dates and sizes)
I don't know if any other files are duplicated in the archive.
There is only one copy of the above files on the site.
The site being backed up is small - the tar.gz file is 21MB (the ZIP file is 17MB) and it performs the backup in about 30 seconds (whichever archive type is selected), so this is not a script timeout.
waht did you have enterd in S3 Folder in bucked field?
i think i have found it i will release an update asap.
Hi,
When editing a BackWPup job
I have just noticed that the archive name compound formula gets changed after being saved.
e.g. ExtList-%Y-%m-%d-%H-%i-%s becomes ExtList--Y--m--d--H--i--s
so then my backup archive file get overwritten
the table char set is general_utf8_ci.
Anyone seen this?
The Folder in bucket field is empty.
I thought it was localized to just the one site, but now this issue is occurring on all of the sites I manage (or at least several that were scheduled to run during the last two days), all with the same error, and nothing changed on those sites other than updating the plugins.
Thanks Daniel! I look forward to the update.
Release 3.1.4 is out with a fix.
I need to back up http://www.naturallycapturedphotography.com but when I try to run the job through BackWPup, this error message occurs: "The HTTP response test get a false http status (500)".
Help, please. What does this mean and how can I fix it? Very green here.
Thank you so much!
Great! That seems to have fixed it. Thanks for the quick fix!
Using the bucket policy provided by Daniel I get the following:
Statement is missing required element - Statement "NO_ID-0" is missing "Principal" element
I just migrated to PHP 5.4 - didn't have this problem. May be time to get more familiar with the inner workings of S3.
BackWpUp creates a Backup role that seems to interfere with Capability Manager. The role can't be removed, even after deleting the BackWpUp plugin.