Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

MInio console UI page refresh issue #3274

Closed
balaKarur opened this issue Mar 27, 2024 · 14 comments
Closed

MInio console UI page refresh issue #3274

balaKarur opened this issue Mar 27, 2024 · 14 comments
Assignees

Comments

@balaKarur
Copy link

balaKarur commented Mar 27, 2024

NOTE

Hello All,
Issue:
Getting refresh issue while access minio Console UI, Please refer attached image...
I faced this issue in both minio (windows and linux version )
To check minio windows version : [https://min.io/download#/agpl-windows]

Expected Behavior

while access minio console UI , logion page has to shown ,without multiple refresh .
http://localhost:9001/

Current Behavior

Need to refresh many time to get login page , after login successful , again need to refresh many time to get landing page

Possible Solution

Need a suggestion to fix this
## Steps to Reproduce (for bugs)

This is windows minio ,
https://min.io/download#/agpl-windows
Just download and run the server you will face refresh issue while access the URL
http://localhost:9001/

## Context

I need to use minio server, for to upload files under bucket .
## Regression

I think .its Regression, and straightforward issue

Your Environment

volumes:
minio_data: (edited)
refresh

@cesnietor
Copy link
Collaborator

@balaKarur could you please share your keycloak configuration, there might be an issue there.
cc @adriangitvitz

@balaKarur
Copy link
Author

Hello @cesnietor
i am getting issue without keycloak integration also

I tried with windows version from below URL
https://min.io/download#/agpl-windows

By following these steps :
PS> Invoke-WebRequest -Uri "https://dl.min.io/server/minio/release/windows-amd64/minio.exe" -OutFile "C:\minio.exe"
PS> setx MINIO_ROOT_USER admin
PS> setx MINIO_ROOT_PASSWORD password
PS> C:\minio.exe server F:\Data --console-address ":9001"

I notioced issue exist in 2 place ,
1)while accessing login page URL. http://localhost:9001
2)while switching inside the bucket http://localhost:9001/browser/bk1

@balaKarur
Copy link
Author

Hello @cesnietor @adriangitvitz
Could you please check for a refresh issue on the Windows version?

@adriangitvitz
Copy link
Contributor

using this configuration with docker works, could you provide your keycloak configuration ? and also are the containers reachable ?

version: "3.8"
services:
  minio:
    image: quay.io/minio/minio:RELEASE.2024-03-21T23-13-43Z
    container_name: minio
    volumes:
      - ./minio_data:/data
    command: server /data --console-address=":9001"
    ports:
      - 9000:9000
      - 9001:9001
    environment:
      - MINIO_ROOT_USER=admin
      - MINIO_ROOT_PASSWORD=Pa55w0rd
      - MINIO_SERVER_URL=http://localhost:9000/
      - MINIO_DOMAIN=http://localhost:9000/
      - MINIO_IDENTITY_OPENID_CONFIG_URL_KEYCLOAK_PRIMARY=http://host.docker.internal:8080/realms/consoletest/.well-known/openid-configuration
      - MINIO_IDENTITY_OPENID_CLIENT_ID_KEYCLOAK_PRIMARY=minio
      - MINIO_IDENTITY_OPENID_CLIENT_SECRET_KEYCLOAK_PRIMARY=6FJmGUdCBbhiDUJCLTZ8zKzqIh6YOC4X
      - MINIO_IDENTITY_OPENID_DISPLAY_NAME_KEYCLOAK_PRIMARY=MinIO OpenID Login
      - MINIO_IDENTITY_OPENID_CLAIM_NAME=policy
      - MINIO_IDENTITY_OPENID_VENDOR=keycloak
      - MINIO_IDENTITY_OPENID_REDIRECT_URI_DYNAMIC_KEYCLOAK_PRIMARY=on
      - MINIO_IDENTITY_OPENID_SCOPES=minio-authorization
      - MINIO_IDENTITY_OPENID_KEYCLOAK_REALM=consoletest
      - MINIO_IDENTITY_OPENID_KEYCLOAK_ADMIN_URL=http://host.docker.internal:8080/admin

@balaKarur
Copy link
Author

@adriangitvitz
"using this configuration with docker works, could you provide your keycloak configuration ? and also are the containers reachable ?"
Thank you for your effort. As I confirmed, the issue is not related to Keycloak. Once Minio is up, did you get time to check if the Minio console UI is accessible by accessing this URL: http://localhost:9001/ without having to refresh multiple times?

I noticed the refresh issue exists in two places:

While accessing the login page URL: http://localhost:9001/
While switching inside the bucket: http://localhost:9001/browser/bk1

@balaKarur
Copy link
Author

@adriangitvitz
I hope this message finds you well. Did you get the time to check the reported issue above? If not, could you please take a moment to review it? Thank you.

@adriangitvitz
Copy link
Contributor

Hi, I don't see the refresh issue while accessing http://localhost:9001/ or http://localhost:9001/browser/bk1, using the previous docker compose configuration.

Screen.Recording.2024-05-06.at.8.05.20.a.m.mov

@cesnietor
Copy link
Collaborator

could you provide your keycloak configuration

@balaKarur we'd need to see your configuration otherwise it's not possible for us to reproduce this.

@balaKarur
Copy link
Author

balaKarur commented May 8, 2024

Hello @cesnietor @adriangitvitz ,
Thanks for your continuous support. i attached keycloak configuration, Please check
This is my yaml file:
version: "3.8"
services:
minio:
image: quay.io/minio/minio:RELEASE.2024-05-07T06-41-25Z
container_name: minio
volumes:
- ./minio_data:/data
- ./certs:/certs
command: server /data --console-address=":9002"
ports:
- 9000:9000
- 9002:9002
environment:
- MINIO_CERTS=/certs/cert.pem
- MINIO_CERTS_KEY=/certs/privatekey.key
- MINIO_ROOT_USER=minio_user
- MINIO_ROOT_PASSWORD=password
- MINIO_SERVER_URL=http://localhost:9000
- MINIO_DOMAIN=http://localhost:9000
- MINIO_IDENTITY_OPENID_CONFIG_URL_KEYCLOAK_PRIMARY=http://host.containers.internal:8088/kc/realms/minio_realm/.well-known/openid-configuration
- MINIO_IDENTITY_OPENID_CLIENT_ID_KEYCLOAK_PRIMARY=minioclient
- MINIO_IDENTITY_OPENID_CLIENT_SECRET_KEYCLOAK_PRIMARY=nVrPspagFouiPniL14ZYmShqcOusuNVZ
- MINIO_IDENTITY_OPENID_DISPLAY_NAME_KEYCLOAK_PRIMARY=MinIO OpenID Login
- MINIO_IDENTITY_OPENID_CLAIM_NAME=policy
- MINIO_IDENTITY_OPENID_VENDOR=keycloak
- MINIO_IDENTITY_OPENID_REDIRECT_URI_DYNAMIC_KEYCLOAK_PRIMARY=on
- MINIO_IDENTITY_OPENID_SCOPES=minio-authorization
- MINIO_IDENTITY_OPENID_KEYCLOAK_REALM=minio_realm
- MINIO_IDENTITY_OPENID_KEYCLOAK_ADMIN_URL=http://host.containers.internal:8088/kc/admin

volumes:
minio_data:

keycloak Configuration Doc
FYI , i followed this document: https://min.io/docs/minio/macos/operations/external-iam/configure-keycloak-identity-management.html
and configured minio in Keycloak
Update keyclock with minio configurations_minio_client.docx

@balaKarur
Copy link
Author

balaKarur commented May 13, 2024

Hello @cesnietor @adriangitvitz ,
Thanks for your continuous support. If you have some free time, could you please check my keycloak configuration?

@adriangitvitz
Copy link
Contributor

@balaKarur please try with the following and let me know, in the home url, after "realms", use your realm name

Screenshot 2024-05-14 at 11 35 01 p m

@balaKarur
Copy link
Author

Hello, @cesnietor, @adriangitvitz ,
Thank you for your support, and I apologize for the delay in my reply.
I tried the way you suggested, but it did not help that solution. Still, I need to refresh multiple times to get login page
A small request: can we connect through Google Meet? to solve this issue?
please let me know when you have free time ,
image

Thanks
Balasubramani.V

@prakashsvmx
Copy link
Member

We request you to consider min.io/pricing @balaKarur .

@cesnietor
Copy link
Collaborator

@balaKarur please refer to what @adriangitvitz suggested.
For more Keycloak configuration support please refer to their page.
Also feel free to use our Slack channel where other community members might be able to help you with support.
For more immediate help definitely consider subscribing to SUBNET (min.io/pricing).
Closing since this is a configuration issue and not a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants