@julien66
could you try to disable all plugins except BackWPUp then run the job again?
Thanks!
Thanks @duongcuong96
Deactivated all plugins except BaxkWPup!
The issue was even worse unfortunately: when I click on the S3 tab, it spins and I have to wait 30s to 1 mn before an almost empty page shows up (with the name of the 3 first tabs but everything else empty).
That’s what I was saying, it’s really odd such a behavior.
@julien66 I have the same use case as you and this was a head scratcher.
I think there are 2 issues here:
(1) On backblaze b2 app key creation, I have contacted their help desk and they have responded that the appkey must include all buckets for the s3 endpoint to work
(2) On backwpup, since the appkey would not be valid, this then throws the error as you described, and there is no way to delete the keys as it is cached and stored in the DB I think.
To workaround this issue (and I have tested that it works) – create new appkey on b2 with all buckets permission, and recreate new job on backwpup and it is critical that we fill up the values in this order: s3 server url, access key, secret key.
side note – there may be a bug somewhere on the plugin on the s3 menu not loading due to error by an invalid key
@jxlow TY for the suggestion, @julien66 is that help?
since we haven’t heard back from you, I’m going to mark it as resolved.
If you’re still having problems, feel free to let us know ;),
btw, if possible, please help us try the new version which fixed the custom S3!
thank you so much!
https://www.dropbox.com/s/hcd4p5tr37m1ivc/backwpup-1474.zip?dl=0
Looking forward to hearing new feedback from you ^^