Setting up MinIO behind a reverse proxy

[ricardoboss]

Select Topic Area

Question

Body

I'm currently trying to set up MinIO with our GitHub Enterprise Server 3.15.

We have MinIO behind a reverse proxy that forwards requests to https://buckets.<redacted>.com to MinIOs port 9000.

Now, with the AWS Service URL set to https://buckets.<redacted>.com and all other credentials filled out, I get the message "Unable to connect to storage provider. Please check the form and try again.".

So, naturally, I ssh'd into the vm (admin@<ip> -p 122) and tried from there. The MinIO command line client mc was already installed and I was able to not only connect to the server but also list buckets and blobs using the same credentials.

Why doesn't it work using the management console web interface? Are there any logs I can view to find out what the problem is?

[ricardoboss]

Okay, as it turns out, the region we set in our MinIO instance was "invalid". Invalid here means it didn't match an existing AWS region. I tried a few values but the only region that worked was "us-east-1", although we are located in Europe...

Not sure who to blame, MinIO seems to have something to do with it (minio/minio#12886) but it could as well be GitHubs tooling using the SDK wrong? Anyways... setting the region to "us-east-1" makes it work.

[queenofcorgis]

We’re glad you could get this solved and we want to make sure others can do the same so we’ve reopened this discussion for better discoverability for our members.