a day ago
Description: Self-hosted S3 storage with a web management dashboard
Category: Storage
4 Replies
4 hours ago
Hi, i have tested this new template, couple of things:
1 - By default, the web don't have a public domain configured, not the big dead, but it would be nice not to have to configure it. (I did it and I was able to log in)
2 - I'm getting an error when the UI load the buckets, this one: Get "garage-s3.railway.internal:3902/v2/ListBuckets": unsupported protocol scheme "garage-s3.railway.internal". No idea whats happening
jesushdez
Hi, i have tested this new template, couple of things: 1 - By default, the web don't have a public domain configured, not the big dead, but it would be nice not to have to configure it. (I did it and I was able to log in) 2 - I'm getting an error when the UI load the buckets, this one: Get "garage-s3.railway.internal:3902/v2/ListBuckets": unsupported protocol scheme "garage-s3.railway.internal". No idea whats happening
3 hours ago
Hi, thanks a lot for testing it and for the detailed feedback, both are really helpful!
1 — Public domain: Good call. I've updated the template so the WebUI service now gets a public domain generated automatically on deploy. Glad you were able to log in in the meantime!
2 — "unsupported protocol scheme" error: That one was on me, the default values for API_BASE_URL and S3_ENDPOINT_URL were missing the http:// scheme prefix. The WebUI's proxy needs a full URL (with the scheme), so garage-s3.railway.internal:3902 fails while http://garage-s3.railway.internal:3902 works. I've fixed the template defaults to include http://.
If you want to fix your current deployment without redeploying from scratch, just edit those two variables on the WebUI service to:
API_BASE_URL = http://garage-s3.railway.internal:3902
S3_ENDPOINT_URL = http://garage-s3.railway.internal:3900
(Use http://, not https://, since it's over the private network.) After that, the bucket list should load fine.
Thanks again for the report.
an hour ago
It now fails due to this:
Get "http://garage-s3.railway.internal:3902/v2/ListBuckets": dial tcp [1111:1111:1111:1:1111:1:1111:1111]:3902: connect: connection refused
jesushdez
It now fails due to this: Get "http://garage-s3.railway.internal:3902/v2/ListBuckets": dial tcp [1111:1111:1111:1:1111:1:1111:1111]:3902: connect: connection refused
23 minutes ago
Thank you for your patience. I've identified the cause of the problem: the Railway's private network uses IPv6, but the Garage administration API was configured to accept only IPv4 connections. Therefore, the WebUI couldn't connect to the service.
We've already published a fix that enables IPv6 support in the administration API. Simply redeploy the Garage S3 service to apply the update.
No environment variables need to be changed. The fix is already included in the Garage startup configuration.
Thank you for sharing the error details; they were crucial in quickly identifying the cause of the problem.