I am having a problem with Duplicacy and Wasabi. I am new the Duplicacy, and after some testing, decided to go with Duplicacy backing up to Wasabi. Everything seemed to be working fine and backing up successfully. However 1st sign of issue was in the middle of the night last night (Sydney/Australia time) at 1:57 I got the error :-
2018-10-29 01:57:27.715 ERROR UPLOAD_CHUNK Failed to upload the chunk 4045b2d894160ed83cf5fc987aa56cd16c4be584e42bb055240f9a0eef6461aa: AccessDenied: Access Denied [01:57:27] C:\duplicacy-matthew Backup operation returned an error: ERROR Failed to upload the chunk 4045b2d894160ed83cf5fc987aa56cd16c4be584e42bb055240f9a0eef6461aa: AccessDenied: Access Denied
After trying to restart it, I get the following error :-
C:\duplicacy-backup>duplicacy -log backup -stats 2018-10-29 15:37:01.567 INFO STORAGE_SET Storage set to s3://email@example.com/duplicacy-other/jjs 2018-10-29 15:37:02.755 ERROR STORAGE_NOT_CONFIGURED The storage has not been initialized
But I know it is configured and working correctly up to that point and in between I had done nothing to change this, other than run backups. Interesting that I have backups going to 2 different buckets, and they all appear to have stopped working at the same time???
I tried accessing Wasabi with other tools and it all seems to be working fine. eg tried web gui to upload files, and also tried S3 access using CyberDuck and as far as I can tell, Wasabi seems to be working fine, so it looks like some sort of compatibility issue with Duplicacy???
I am not sure if this might be a little clue, but initially suspecting an issue with Wasabi I went to check out Wasabi via the Web console. When I tried to sign on to the console via HTTP I got a swirling Wasabi icon in the web interface that went nowhere. This seemed to affect any PC/Browser, I had previously accessed Wasabi on, but did not affect browsers or PCs I had not accessed Wasabi console on. To fix this, I did a “hard refresh” which is CTRL reload in Chrome and all seemed to work again for web access to the console. I have never had this issue before, but don’t like coincidences so wonder if this issue is related (ie Wasabi have made some changes overnight which caused this problem and broke Duplicacy access to Wasabi.
I have also tried a number of things to get it going. At 1 point I wondered if somehow my Data or bucket had got corrupted, so I created a new bucket and tried a test backup to that Bucket. I did this in the GUI and I got throguht to entering the encryption password, but when I did that I got the error message back “ERROR Failed to configure the storage: AccessDenied: Access Denied”. I even tried doing this to a different Wasabi account in case my account had become corrupted. But nothing worked. But if I access with another tool like CyberDuck, I can’t see any sign of an issue.
I have Duplicacy backing up to a 2nd store (local SFTP) and that seems to be working fine.
So to me it seems like there might have been some change to Wasabi overnight that is causing compatibility problems with Duplicacy and I am stuck.
Note : I am using us-west-1.
Are other people able to still access backups on Wasabi and in particular us-west-1? Any ideas how to fix this problem as I have a lot of Data backed up now and want to avoid having to start again.
Thanks in advance.