Trying to set up against minio

Support
1

Hi there

I’m trying get a linux box set up with duplicati towards QUObjects and I’ve also tried with minio.

I can get duplicati 2.2.0.1 to work against my iDriveE2 subscription, but I really want to get out of that.

As I have an old QNAP that has been decomissioned, it was obvious for me to use that as an S3 target, QNAP has their own QUObjects application for that.

So after spending most of 2 weeks working every possible angle on this, chatgpt tells me that all 2.1 and 2.2 versions have broken s3 interfaces, and recommended me installing Duplicati - 2.0.8.1_beta_2024-05-07

It said:

Duplicati 2.2.0.x (Experimental builds)

They shipped with a broken S3 backend loader.

I know 2.2.0.x is no longer experimental, but still…

So I did, and now my backup works with QUObjects, no need for minio in a container.

Is that really true, do I need to go that far back?

Access keys looks weird in QUObjects (with a : in it), but I got the same errors with minio.
no path allowed in endpoint

So I installed 2.0.8.1_beta and the backup runs perfectly to my QUObjects.

Now what to do? I really would like to go to a newer version of duplicati both on the linux and windows box I’m testing with, but of course I need to have a working connection.

2

Gave up on Minio, and went back to QUObjects, and I got it working! I will make a video about how this is to be configured, because that is REALLY odd.

3

I doubt it. Even though not everything is in Issues, broken S3 would likely be.

is:issue in:title s3 OR in:title aws as query shows history of issues.
Some are pretty narrow, involving specific setups, and these can be difficult…
Sometimes the developers can advise on solutions among S3 options. I can’t.

4

I got it working towards QUObjects, the minio version you can download now is crippled, it has gone payware.