3 months ago
I created a new bucket in my project and it says to use virtual-hosted-style url's at the bottom of the credentials, which matches what the docs say. However, trying to connect using virtual-hosted-style url's does not work. Instead I have to use path-style url's to connect. I'm using bun's s3 client and for presigned url's they have to be path-style, trying to use virtual-hosted-style results in 500 error.
This is a new bucket created after the official announcement. The docs seem to suggest that maybe this behavior changed at some point in the development of the feature?
Anyways, why am I having to use path style url's? Is something wrong? Is this going to change?
4 Replies
3 months ago
Hey there! We've found the following might help you get unblocked faster:
If you find the answer from one of these, please let us know by solving the thread!
3 months ago
Hello !!Jake,
It's likely that the pre-signed method is going to require you to use the path style. I am going to relay this question over to the engineer to see where the shortcoming is.
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
okay interesting, look forward to any more information you can share from them. thanks
Status changed to Awaiting Railway Response Railway • 3 months ago
3 months ago
Hi Jake, I'm Product Engineer here working on Buckets.
Could you share a relevant code snippet and your environment variable configuration (of course with redacted key id and secret), so that I can try to reproduce?
Presigned URLs with virtual-hosted–style URLs should work, I'm using them myself.
Thanks in advance!
Status changed to Awaiting User Response Railway • 3 months ago
3 months ago
This thread has been marked as solved automatically due to a lack of recent activity. Please re-open this thread or create a new one if you require further assistance. Thank you!
Status changed to Solved Railway • 3 months ago