#Minio

26 messages · Page 1 of 1 (latest)

jaunty totem
#

There are currently two services deployed as described in the docs, "Bucket", "console". I have configured two subdomains

1 - console.domain.level
2 - files.domain.level
navigating to console.domain.level displays the minio console as expected, but files.domain.level redirects to subdomain.railway.app. 1, What's causing the redirect and 2 which one of these subdomain should I use to upload files and make accessible publicly?

https://railway.app/template/SMKOEA

raw cargoBOT
#

Project ID: e349bbb7-fbe9-42d8-be7f-52bd0bd1c3a0

proud garnet
#

subdomain.railway.app - please provide actual domains.

jaunty totem
#

project is e349bbb7-fbe9-42d8-be7f-52bd0bd1c3a0

#

The domains in questions are
static.brebo.dev and files.brebo.dev

proud garnet
#

have you redeployed both services since adding your custom domains?

jaunty totem
#

I have not re redeployed any of the services since adding my custom domains.

proud garnet
#

please go ahead and do that

jaunty totem
#

I just did. Now, static.brebo.dev redirect to files.brebo.dev.

proud garnet
#

perfect!

jaunty totem
#

I was under the impression I would use files.brebo.dev to mange minio and static.brebo.dev upload and serve files?

proud garnet
#

thats correct

jaunty totem
#

Thanks!

proud garnet
#

no problem!

rigid gustBOT
jaunty totem
#

I think the reverse proxy might not be configured correctly. I can not login to the console anymore after restart.

proud garnet
#

what reverse proxy?

jaunty totem
#

the proxy that's in front of the minio service

#

I think that's internal to railway. I don't have access to that service.

#

This is what I am seeing in the logs

Docs: https://docs.min.io

INFO: Exiting on signal: TERMINATED

ErrorWithContext:The authorization header is malformed; the region is wrong; expecting 'us-east-1'.

%!(EXTRA *errors.errorString=invalid login)

Stopping Container

ErrorWithContext:The authorization header is malformed; the region is wrong; expecting 'us-east-1'.

%!(EXTRA *errors.errorString=invalid login)
proud garnet
#

where can i see this error for myself?

jaunty totem
#

I can't find the deployment id for the minio instance. I assume it's the first part of this railway subdomain? console-staging-c7ff.up.railway.app

proud garnet
#

those are logs the app is printing, not railway

proud garnet
#

i just deployed minio, added custom domains to both console and bucket, redeployed both, and i can't reproduce this error.

i recommend you redeploy the template from scratch, you may have missconfigured something along the way.

jaunty totem
#

Thanks, I will try again!

#

I wiped the volume, restarted both the console and bucket. I am able to login again.