@Recliner2042 Or even two remote servers. One compute VPS and one storage VPS, for example.

@taowang peertube stores files in the filesystem (by default). If you check the configuration file (https://docs.cloudron.io/apps/peertube/#customization) , you can see the paths. Change the paths to that of the your mount.

The S3 stuff comes into picture only if you configure peertube to use "object storage" (i.e remote storage, I think in peertube lingo)

@girish said in Mino on Cloudron serving files using IPFS:

@LoudLemur do you mean the 6th slide? I think this involves installing ipfs on the server (which is not part of minio).

I see. Since installing additional software onto the operating system is a no-no for Cloudron, this would therefore not be ok.

With the latest update which brings up the memory limit to min 2GB, things look better in my instance.

@nebulon Yes, some of the apps are not compatible with Cloudflare. Maybe Cloudflare users have to test it. Thank you for the support Cloudron team! 🙂

@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?

@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.

The only way Minio operates with externals is if it is being used as a mirror, or, "bucket replication". Even then, the destination of the replicated bucket has to also be on a Minio system. Your best approach is to install ONE Minio system, externally, and then setup Cloudron to backup (and backup it's backups) to THAT external Minio.

@timconsidine I have been backing up to scaleway on NL region ~10 days or so and haven't hit any issues. I will switch to Paris and see.

@Gaurav https://docs.cloudron.io/apps/#memory-limit

@cyberfreakde join their Slack and ask there.

@girish Thanks for your response.
I'll report this on Github...

@Lanhild I am afraid I need more information to help. What did you try? Did you try s3cmd and get same error? Can you paste the error output?

Unfortunately, it seems they removed the previous fs backend entirely and there is no automatic migration.

I guess we have to make a new package. Their migration guide is at https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html

@felixbmmm said in MinIO: Infinite loading when previewing or downloading file:

I ran MinIO's docker image then access its browser console

Just to double check, are you even using Cloudron ? This is the forum for the minio package on Cloudron (and not for the upstream docker image). Upstream questions should be posted at https://github.com/minio/minio/discussions

@girish Thank you

@girish yay ! 🍾
Despite the hour I couldn't resist trying it.
I changed the location of the api from minio-api.domain.tld to minioapi.domain.tld (just removed the hyphen) and saved the change.
Renewed certs and logs now show the api domain in there.
Tested with Minio mc CLI and Forklift : they both list buckets and contents.
Will check MountainDuck and others later.

Thanks for your patience and support.
Marking it solved ! 🍾

I did a full run of update testing now.

After upgrade, I was able to login with my previous root credentials.

After upgrade, indeed, the env variables are not injected. I have put an example in docs now - https://docs.cloudron.io/apps/minio/#admin-credentials . New installs have these variables.

I was able to reproduce the clone issue. Was easy to fix. I guess this will be useful in case one wants to inspect older backups in the future.

The restore is a bit more complex - Made an issue https://git.cloudron.io/cloudron/box/-/issues/814