# MinIO installer failing again, this time with a HTTP 410

**URL:** https://meta.discourse.org/t/minio-installer-failing-again-this-time-with-a-http-410/412290
**Category:** Support
**Created:** [12 september 2026 om 20:15 UTC](https://meta.discourse.org/t/minio-installer-failing-again-this-time-with-a-http-410/412290 "2026-09-12T20:15:18Z")
**Posts on this page:** 1
**Showing post:** 3

<div class="post-metadata">

### Author: ![merefield](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/merefield/32/176214_2.png) [@merefield](https://meta.discourse.org/u/merefield)
#### Post date: [13 september 2026 om 06:43 UTC](https://meta.discourse.org/t/minio-installer-failing-again-this-time-with-a-http-410/412290/3 "2026-09-13T06:43:38Z")

</div>

Yeah.

Looks like:

- Both `minio/minio` and `minio/mc` are now archived.
- MinIO’s README says “ **Alternatives:** \* **[AIStor Free](https://min.io/download)** — Full-featured, standalone edition for community use (free license)”
- MinIO’s README also says “ **Important:** The MinIO community edition is now distributed as source code only. We will no longer provide pre-compiled binary releases for the community version.”

I’m not sure if AIStor is a simple drop-in replacement?

Given this simply just doesn’t work now, is it better to disable this dependency and skip any tests that rely upon it in interim?

I appreciate specs are critical but I believe this is only used on a _tiny_ percentage of tests.

Does this break production in some way? From my analysis, impact looks limited to specs?

---

_[View the full topic](https://meta.discourse.org/t/minio-installer-failing-again-this-time-with-a-http-410/412290)._