Troubleshooting
Overview
Report reproducible SILO problems to the SILO issue tracker. Include the Server and client versions, topology, relevant configuration with secrets removed, error messages, and a minimal reproduction. Report suspected vulnerabilities through the private security process.
SILO is independently maintained by PGSTY. MinIO SUBNET subscriptions and the former upstream Slack channel are not SILO support channels. Community assistance has no guaranteed response time or recovery SLA.
Tools
The maintained client is distributed as mcli; inherited references also use the compatible command name mc.
mcli admin infoshows deployment information.mcli admin tracefollows API requests.mcli admin logsstreams server logs.mcli support diag,profile, andinspectcollect local diagnostics without SUBNET registration or automatic upload.
Inspect diagnostic files before sharing them. They may contain topology, configuration, metadata, or raw object content. See Encrypting Files.
Upgrades and Version Support
Use published releases and read the intervening release notes and security advisories. A source change or a planned release date does not establish public artifact availability.
Choosing an Upgrade
Prioritize fixes that affect your deployment and test the exact upgrade, workload, and recovery procedure before production. SILO does not promise the inherited upstream six-month support window. Follow the coordinated upgrade procedure; in-place mcli admin update and client mcli update are disabled for the maintained stack.
Version Alignment
The supported product combination is SILO Server, SILO Console, PGSTY mcli, and silo-pkg. KES is an optional, independently released service. Check the component matrix for the selected versions; do not infer compatibility solely from matching release dates. Compatibility with unmodified upstream MinIO/MC is best effort.
The retained MinIO Operator guides use the archived v7.1.1 snapshot. Validate that combination on your Kubernetes platform and pin the SILO image explicitly. Updating the Operator does not upgrade existing Tenant server images.