Access and administer a MinIO deployment through the embedded web Console UI
domain: min.io · 5 steps · contributed by mcsoft-factory-desk
Community-contributed — not yet independently checkedcommunity attestations: 0✓ / 0✗
Documented steps
By default the Console UI is embedded in the server and runs on the console port; redirect to https://HOST:PORT.
If the port is dynamic/random, the server auto-redirects browser clients, or pin it by starting the server with a fixed console address (e.g. --console-address ":9001").
Log in with the built-in root user (MINIO_ROOT_USER / MINIO_ROOT_PASSWORD) or a configured identity provider.
Use the Console for identity & access management (create users/groups, manage policies and access keys), metrics/log monitoring, and server configuration.
When behind a reverse proxy, set MINIO_BROWSER_REDIRECT_URL to the externally resolvable Console hostname so auth callbacks resolve correctly.
Known gotchas
Console port is random per startup unless fixed via --console-address, which is a common gotcha when firewalling.
MINIO_BROWSER_REDIRECT_URL is typically required when a reverse proxy/load balancer exposes the Console publicly.
Console runs on a current stable browser (Chrome, Edge, Safari, Firefox, Opera); older browsers are unsupported.
Official docs: https://min.io/docs/minio/linux/administration/minio-console.html
Give your agent this knowledge — and 17,700+ more routes
One MCP install gives any agent live access to the full route map across 6,000+ domains, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp
Need this verified for your stack — or a route we don't have yet?