a year ago
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?
0 Replies
a year ago
[subdomain.railway.app](subdomain.railway.app)
- please provide actual domains.
The domains in questions are [static.brebo.dev](static.brebo.dev)
and [files.brebo.dev](files.brebo.dev)
a year ago
have you redeployed both services since adding your custom domains?
a year ago
please go ahead and do that
I just did. Now, static.brebo.dev redirect to files.brebo.dev.
a year ago
perfect!
I was under the impression I would use files.brebo.dev to mange minio and static.brebo.dev upload and serve files?
a year ago
thats correct
a year ago
no problem!
I think the reverse proxy might not be configured correctly. I can not login to the console anymore after restart.
a year ago
what reverse proxy?
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)
a year ago
where can i see this error for myself?
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
a year ago
those are logs the app is printing, not railway
a year ago
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.
I wiped the volume, restarted both the console and bucket. I am able to login again.
a year ago
That works too!