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

Unable to change access policy for the bucket. #3125

Closed
h56983577 opened this issue Nov 10, 2023 · 4 comments
Closed

Unable to change access policy for the bucket. #3125

h56983577 opened this issue Nov 10, 2023 · 4 comments
Assignees

Comments

@h56983577
Copy link

h56983577 commented Nov 10, 2023

NOTE

I'm new to Minio and just started exploring it today, so I can't tell whether this is a bug or a feature. This issue has been confusing me, and I can't find an answer through the Internet.

Expected Behavior

After creating a bucket, I would like to set it as public directly.

Current Behavior

When I click the 'Set' button, there is no response. Upon checking the network request history, I found that the request to /api/v1/buckets/file2/set-policy failed, with the message net::ERR_CONNECTION_RESET.
image
image

This is the body of the request.
image

Steps to Reproduce (for bugs)

  1. Create a new bucket.
    image

  2. Access the management interface of the bucket.
    image

  3. Switch to 'Public' and click the 'Set' button.
    image

  4. Then, I saw the error message.
    image

Context

I want to quickly set up a testing bucket for personal application development, not for production use. So I set it to public directly.

Your Environment

  • MinIO version used (minio --version):
minio version RELEASE.2023-11-06T22-26-08Z (commit-id=754f7a8a395e87a744050476d8b16c16af50a800)
Runtime: go1.21.3 linux/amd64
License: GNU AGPLv3 <https://www.gnu.org/licenses/agpl-3.0.html>
Copyright: 2015-2023 MinIO, Inc.
  • Server setup and configuration:
    I run this Minio server using Docker.
docker run -p 9000:9000 -p 9090:9090 --name minio \
  -d --restart=always \
  -e "MINIO_ACCESS_KEY=admin" \
  -e "MINIO_SECRET_KEY=admin123456" \
  -v /data/minio/data:/data \
  minio/minio:RELEASE.2023-11-06T22-26-08Z \
  server /data --console-address ":9090"
  • Operating System and version (uname -a): Linux ubuntu2004 5.4.0-166-generic
@prakashsvmx
Copy link
Member

Could you please try with mc anonymous set public ALIAS/bucket

https://min.io/docs/minio/linux/reference/minio-mc/mc-anonymous-set.html

@h56983577
Copy link
Author

Could you please try with mc anonymous set public ALIAS/bucket

https://min.io/docs/minio/linux/reference/minio-mc/mc-anonymous-set.html

Thank you! I successfully set it to 'Public' using the mc anonymous command.

@h56983577
Copy link
Author

@prakashsvmx I'm so sorry. I found that PUT requests are not allowed in my internal network environment, which leads to the error mentioned above. This is not a bug of the Minio console itself.

@prakashsvmx
Copy link
Member

Sure. thank you, I have verified this on our hosted instance and local env. it is working as expected.

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

2 participants