How to connect a MinIO bucket to file.rocks
If you run MinIO yourself, file.rocks can use it like any other S3 bucket. Your files stay on your server, and you browse and upload from file.rocks.
It's the same form as the Amazon S3, Cloudflare R2, Backblaze B2 and Wasabi guides. The part that's different with MinIO is the endpoint.
1. Before you start
file.rocks servers list your bucket, and your browser uploads files straight to it. That means your MinIO endpoint has to be reachable from the internet, over https.
Https matters because file.rocks runs on https. Browsers block an https page from sending files to a plain http address, so an http endpoint won't take uploads.
Have these ready:
- Your MinIO API endpoint, starting with
https:// - An access key and secret key that can read and write the bucket
- The bucket name
- The region, if your MinIO server has one set
MinIO's docs say the default CORS setting allows all origins, and that CORS rules set on a bucket are used instead of the global setting (MinIO CORS configuration). If you've narrowed CORS on your server or on the bucket, make sure it allows https://www.file.rocks.
2. Open the bucket form
Go to Settings, then Buckets, and click Add Bucket. If you don't have any buckets yet, the button reads Create your first bucket.
The Create Bucket window opens. Under Storage Type, pick Bring Your Own. You don't need a paid plan to add your own bucket.
Open Provider and choose Minio.
3. Fill in the fields
Access Key ID and Secret Access Key
Paste your MinIO access key into Access Key ID and the secret into Secret Access Key. The example values in those boxes are AWS-style placeholders, so ignore them.
Endpoint
Endpoint is the address of your MinIO API, not the web console. Start it with https://, and add the port if you use one, like https://minio.example.com:9000.
The box starts empty, and its placeholder shows an Amazon address. Replace it with yours.
Don't skip the https://. Without it, file.rocks treats the bucket as Amazon S3 and never talks to your server.
file.rocks uses path-style addresses for MinIO, like https://minio.example.com:9000/your-bucket/file.jpg. You don't need wildcard DNS for bucket subdomains.
Bucket Name
Bucket Name is the exact name of the bucket on your MinIO server.
Region
If your MinIO server has a region set, type it into Region. The placeholder shows us-east-1.
When you click out of Endpoint or Bucket Name, file.rocks may fill in Region for you. Check what's there before you save.
Nickname (optional)
Nickname (optional) is the name you'll see in file.rocks. MinIO buckets don't have an Internal name field.
4. Save the bucket
Click Save Bucket. The window closes, the bucket shows up in your Buckets list, and it becomes the bucket you have open.
file.rocks doesn't test the connection when you save, so a typo still saves. The upload in the next step is the real test.
5. Check it with an upload
Open Files and drop in a small file. If it shows up, you're connected.
If Files shows an error or stays empty, go back and check these:
- Endpoint: the API address, starting with
https://, and reachable from the internet - Access Key ID and Secret Access Key
- Bucket Name
- Region
- CORS, if your existing files show up but uploads fail
For more on uploading, see how to upload files to your own bucket.
6. What's different from the other guides
Uploads go straight from your browser to MinIO with a signed link. They don't pass through file.rocks servers, so there's no 32 MB per file limit like the SFTP guide has.
file.rocks doesn't set CORS for you. There's no CORS switch like Backblaze has, and no Public Domain field like Cloudflare R2 has.
On the Usage page, Est. storage / mo shows $0.00 for a MinIO bucket. file.rocks doesn't put a price on storage you host yourself.
Sync works like it does for any S3-compatible bucket. How to sync files between your own buckets covers the setup. If you're weighing hosted storage too, see cheapest cloud object storage.
Your files stay in the bucket you connected, and file.rocks is how you manage them.