mirror of
https://github.com/minio/minio.git
synced 2025-11-07 12:52:58 -05:00
use expected MinIO URLs for console (#12770)
when TLS is configured using IPs directly might interfere and not work properly when the server is configured with TLS certs but the certs only have domain certs. Also additionally allow users to specify a public accessible URL for console to talk to MinIO i.e `MINIO_SERVER_URL` this would allow them to use an external ingress domain to talk to MinIO. This internally fixes few problems such as presigned URL generation on the console UI etc. This needs to be done additionally for any MinIO deployments that might have a much more stricter requirement when running in standalone mode such as FS or standalone erasure code.
This commit is contained in:
@@ -216,6 +216,11 @@ For deployments behind a load balancer, proxy, or ingress rule where the MinIO h
|
||||
|
||||
For example, consider a MinIO deployment behind a proxy `https://minio.example.net`, `https://console.minio.example.net` with rules for forwarding traffic on port :9000 and :9001 to MinIO and the MinIO Console respectively on the internal network. Set `MINIO_BROWSER_REDIRECT_URL` to `https://console.minio.example.net` to ensure the browser receives a valid reachable URL.
|
||||
|
||||
Similarly, if your TLS certificates do not have the IP SAN for the MinIO server host, the MinIO Console may fail to validate the connection to the server. Use the `MINIO_SERVER_URL` environment variable and specify the proxy-accessible hostname of the MinIO server to allow the Console to use the MinIO server API using the TLS certificate.
|
||||
|
||||
For example: `export MINIO_SERVER_URL="https://minio.example.net"`
|
||||
|
||||
|
||||
| Dashboard | Creating a bucket |
|
||||
| ------------- | ------------- |
|
||||
|  |  |
|
||||
|
||||
Reference in New Issue
Block a user