Static Port Assignment for MinIO #575

Closed
opened 2026-02-04 20:02:48 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @mvilrokx on GitHub (Mar 3, 2025).

🌟 Briefly describe the feature

Static Port Assignment for MinIO instead of dynamic port assigment

📝 Detailed description

MinIO has a feature, that by default selects a random port for the MinIO Console on each server startup.

Alternatively, you can select an explicit static port by passing the minio server --console-address commandline option when starting each MinIO Server in the deployment.

Deployments behind network routing components which require static ports for routing rules may require setting a static MinIO Console port. For example, load balancers, reverse proxies, or Kubernetes ingress may by default block or exhibit unexpected behavior with the the dynamic redirection behavior.

It would be nice if the default of the script is to set a static port (9001) as (most?) users will want to use a reverse proxy and I have not been able to get this to work with the dynamic port.

Alternatively, maybe we can have users choose between the 2 options, and even pick a port if they pick the static option.

💡 Why is this useful?

This is useful because otherwise it is impossible to setup a Reverse Proxy to the MinIO service.

Originally created by @mvilrokx on GitHub (Mar 3, 2025). ### 🌟 Briefly describe the feature Static Port Assignment for MinIO instead of dynamic port assigment ### 📝 Detailed description MinIO has a [feature](https://min.io/docs/minio/linux/administration/minio-console.html#static-vs-dynamic-port-assignment), that by default selects a random port for the MinIO Console on each server startup. Alternatively, you can select an explicit static port by passing the [`minio server --console-address`](https://min.io/docs/minio/linux/reference/minio-server/minio-server.html#minio.server.-console-address) commandline option when starting each MinIO Server in the deployment. Deployments behind network routing components which require static ports for routing rules may require setting a static MinIO Console port. For example, load balancers, reverse proxies, or Kubernetes ingress may by default block or exhibit unexpected behavior with the the dynamic redirection behavior. It would be nice if the default of the script is to set a static port (`9001`) as (most?) users will want to use a reverse proxy and I have not been able to get this to work with the dynamic port. Alternatively, maybe we can have users choose between the 2 options, and even pick a port if they pick the static option. ### 💡 Why is this useful? This is useful because otherwise it is impossible to setup a Reverse Proxy to the MinIO service.
OVERLORD added the enhancement label 2026-02-04 20:02:48 +03:00
Author
Owner

@mvilrokx commented on GitHub (Mar 3, 2025):

For reference, I changed this line to be:

ExecStart=/usr/local/bin/minio server --console-address ":9001" /data
@mvilrokx commented on GitHub (Mar 3, 2025): For reference, I changed [this line](https://github.com/community-scripts/ProxmoxVE/blob/0ae7f3b4455270f0f24f61d1d2b8949c626a15c8/install/minio-install.sh#L60) to be: ``` ExecStart=/usr/local/bin/minio server --console-address ":9001" /data ```
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#575