Make Cloudron Minio support virtual host style buckets (possibly requires adding domain alias to Minio app? Or perhaps not?)

[jdaviescoates]

@scooke said in Amazing app to help with backups and saving space!:

Here is a bit more info:
For the Minio buckets to work with Mastodon, Peertube, XBackBone, and another restic-based backup solution I set up, you MUST enter new A records for the bucket and domain of your Minio setup. I don't know how it will work on Cloudron, but for my installed-by-hand Minio instance on my KS-1, I had buckets like peertube-bucket, restic-backup, mastodon-bucket, etc. My Minio instance domain is https://minio.example.com. So, I needed to make (new) A records like:

A minio.example.com ip123
A peertube-bucket.minio.example.com ip123
A restic-backup.minio.example.com ip123
A mastodon-bucket.minio.example.com ip123

After those were active, I then had to rerun sudo certbot certonly --standalone -d minio.example.com -d peertube-bucket.minio.example.com -d restic-backup.minio.example.com -d mastodon-bucket.minio.example.com -d and then copy the two new certs into the proper place (I imagine the Cloudron-based Minio will do all this automatically?)(Certbot calls this "Expanding" the certificate, and I actually added Expanded the two certs three times, rerunning the certbot certonly --standalone with all previous domains, plus whichever was the new one. It didn't work to make a new separate cert, even with it's own A Record, for, for example, resti-backup.minio.example.com plus the original minio,example.com cert. Again, I don't understand completely, but access to Minio depended on there being ONE cert with as many additional domains as necessary within it.) I tried to just use a wildcard entry for the certbot (*.minio.example.com) but it didn't work.

I'm trying to use a Cloudron hosted instance of Minio to back-up some non-Cloudron hosted instances of WordPress that I help manage, and I think it's not working because of this issue.

I think perhaps the Cloudron Minio app needs to have the domain alias feature added like the WordPress (Developer) App has for use with multi-sites, so that when we have set our Minio API url to minio-api.example.coop and create a bucket called bucket-name we can also add an alias bucket-name.minio-api.example.coop.

[jdaviescoates]

@jdaviescoates said in Add domain alias to Minio app:

I'm trying to use a Cloudron hosted instance of Minio to back-up some non-Cloudron hosted instances of WordPress that I help manage, and I think it's not working because of this issue.

I think perhaps the Cloudron Minio app needs to have the domain alias feature added like the WordPress (Developer) App has for use with multi-sites, so that when we have set our Minio API url to minio-api.example.coop and create a bucket called bucket-name we can also add an alias bucket-name.minio-api.example.coop.

Saying that, I tried manually creating the relevant A records but I still can't get BackWPup nor UpdraftPlus to work

[jdaviescoates]

@jdaviescoates said in Help getting Cloudron Minio working with WordPress backup plugins (BackWPup or UpdraftPlus):

@jdaviescoates said in Help getting Cloudron Minio working with WordPress backup plugins (BackWPup or UpdraftPlus):

But that does leave me wondering: is minio really able to do path style buckets and not virtual host style? Because I was under the impression that path-style is the old way

It seems it should be possible to get Minio to accept virtual host style buckets by adding MINIO_DOMAIN=minio.example.net to env.sh - so out of interest I tried that, but it still doesn't work.

@staff are you able to get Cloudron Minio to work with virtual host style buckets?

[girish]

Right, as you noted, for this feature we need to be able to set aliases to the secondary domains and not the primary domain. This needs platform support.

[fbartels]

In general it would probably be better if you could setup some kind of wildcard domain entry, so that all Subdomains of the minio domain map to minio.

[girish]

@fbartels the minio app has two http servers. One for the frontend (primary) and one for the api (secondary). The existing domain alias feature maps the alias into the primary http server. We also support wildcard domain entries in aliases. But for minio, we want the domain alias feature to make into the secondary http server.

[fbartels]

Yes true. With the way minio nowadays works all these aliases need to map to the backend.