Failed to add IDrive E2 storage

Support
#1

Nothing has changed on my end. And never had issues before. But now when I try to add a new storage via the GUI for an IDrive bucket, I get the following error:

Failed to check the storage at s3://e2@XXXXXXX/documentbackup: RequestError: send request failed

The XXXXX above is just to hide some of the output.

I can use the bucket outside of Duplicacy fine using the aws-cli command, etc.

I’ve already removed and re-created the bucket but always get the same error.

Existing IDrive buckets continue to work via Duplicacy’s web gui.

My paid license is still valid

#2

Can you show more logging?

Try adding the storage in the command line to the temporary repository, with the verbose logging enabled (-v).

On the same computer? Maybe DNS issue?

#3

Yes it’s on and from the same computer. As I stated, existing buckets can be accessed/used without issue. There is only a problem creating new storage.
Definitely NOT an DNS issue.

#4

Post the log with -v of an init in a separate repo with CLI.

#5

I was finally able to get this to work. The logs were showing an issue reaching the endpoint.

From the IDrive dashboard, I deleted the bucket and re-created it again.

I had the same error, so I tried to ping the endpoint URL for that bucket and the ping failed.

However I could ping all of the other existing buckets.

I deleted the bucket and re-created it once more.

Still failed to ping. So I deleted the bucket once more but this time created another new one with a different name and BAM, it worked this time.

So there was some weird glitch with IDrive that I failed to reach the new bucket with the initial name I choose for it but when I created another one with a different name it worked.

And yes, the name I initially chose was valid, so no idea why it didn’t work with it.

#6

I almost subscribed to iDrive, and when I saw all the problems on various forums (here too) I didn’t take the plunge. I have 2 backups points, but on the advice of the forum, I think I’ll make a 3rd one on Storj.

(I have one at Hetzner, a Storage Box, works like clockwork for 2 years in SSH/SFTP with Duplicacy, the only problem for the moment is depending on the hours and days, the transfers are not very fast, it’s the price to pay for cheap, on the other hand it is stable, and snapshots are practical in case of disaster)

#7

If it was the only glitch with iDrive…

I strongly recommend migrating to another storage provider. IDrive is horrible, shameless, and spinelsss company. They have been caught more than once shilling for themselves, including on this forum. They were not even competent enough to even try to cover the tracks. Or maybe they don’t care. Yes, that’s likely it.

Please stop giving them money and your time.