Can't login to MinIO console with admin account or self created account.

[jaggerwang]

Expected Behavior

Login to MinIO console.

Current Behavior

It always stay in login page after enter access key(admin) and secret key which are created when creating cluster.

But I can login to the embedded console of MinIO with admin account.

Possible Solution

Tried to create another admin account, but got the same result.

mc admin user add kuangsha-minio-cluster/
mc admin policy add kuangsha-minio-cluster consoleAdmin minio/consoleAdmin.json
mc admin policy set kuangsha-minio-cluster/ consoleAdmin user=console

minio/consoleAdmin.json:

{
    "Version": "2012-10-17",
    "Statement": [{
            "Action": [
                "admin:*"
            ],
            "Effect": "Allow",
            "Sid": ""
        },
        {
            "Action": [
                "s3:*"
            ],
            "Effect": "Allow",
            "Resource": [
                "arn:aws:s3:::*"
            ],
            "Sid": ""
        }
    ]
}

Context

MinIO console log:

2021-03-24 10:02:12.557783 I | 2021/03/24 10:02:12 server.go:129: Serving console at http://[::]:9090
2021-03-24 10:02:12.558641 I | 2021/03/24 10:02:12 server.go:129: Serving console at https://[::]:9443

MinIO Ingress:

apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  annotations:
    nginx.ingress.kubernetes.io/backend-protocol: HTTPS
  name: minio-cluster-console
spec:
  rules:
  - host: minio-cluster-console.dev.bbdops.com
    http:
      paths:
      - backend:
          serviceName: minio-cluster-console
          servicePort: https-console
        path: /
        pathType: ImplementationSpecific

Your Environment

• Version used (minio-operator): v4.0.2
• Environment name and version (e.g. kubernetes v1.17.2): Kubernetes v1.18.14 created by Rancher RKE
• Server type and version: CentOS Linux release 8.3.2011
• Operating System and version (uname -a): Linux dev-kubenode1 4.18.0-240.1.1.el8_3.x86_64 Add Minio operator  #1 SMP Thu Nov 19 17:20:08 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

[Alevsk]

@jaggerwang is the login request returning the session token? please check the server is setting the token in the cookie too, make sure you have cookies enabled, also please try on different browsers and incognito mode, this seems to be a browser issue

[jaggerwang]

@Alevsk I'm using newest Chrome, and I'm sure the cookie is enabled. I also tried on Safari, it's the same result.

But I can access the following MinIO console which deployed by myself to manage another minio service which is not deployed by MinIO operator.

[jaggerwang]

@Alevsk Still the same when upgrade to the newest 4.0.5 version. And I found that I can only pass request to https port of service in ingress, if passing to http port it always got 404 error.

[misastovicek]

Same issue here. It worked until I tried to kill the Minio pods one by one as it will be quite usual on Kubernetes cluster with nodes auto-scaling. I also tried to update minio as well as the console and it is still the same.

Tested in MS Edge + incognito mode and Firefox + incognito mode.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed after 21 days if no further activity occurs. Thank you for your contributions.