3 months ago
alright so i dropped presigned urls and now i'm trying to do uploads from my backend. works fine with s3 and digital ocean spaces. on railway i get this:
error: ERR_TLS_CERT_ALTNAME_INVALID fetching "https://durable-duffel-gkinoymjc3.ams.t3.storageapi.dev/f058bafb-b9cc-4714-872b-b7e4d1e6c9d8.webp?x-id=PutObject". For more information, pass `verbose: true` in the second argument to fetch()
path: "https://durable-duffel-gkinoymjc3.ams.t3.storageapi.dev/f058bafb-b9cc-4714-872b-b7e4d1e6c9d8.webp?x-id=PutObject",
errno: 0,
$metadata: {
attempts: 1,
totalRetryDelay: 0,
},
code: "ERR_TLS_CERT_ALTNAME_INVALID"
totalRetryDelay: 0,
},
code: "ERR_TLS_CERT_ALTNAME_INVALID"12 Replies
oh, i was supposed to drop the region. got it. this still makes zero sense, though, because now i have to build different urls depending on whether i’m using s3 locally or railway buckets in production, since using railway buckets for local development isn’t possible.
what is this API 😭 😭 😭
3 months ago
Using Railway Buckets in local development is possible, all the credentials are in the credentials tab and can be easily added to your service by clicking the button
Attachments
3 months ago
No? <:kekw:788259314607325204>
i know where the credentials are. if i didn't i wouldn't have been able to upload anything at all.
3 months ago
But you said that it isn't possible to use it on local development and then I showed you where you can get those credentials to use on local development environments
3 months ago
It is acessible
Attachments
3 months ago
For reference, the Railway buckets is a wrapper of Tigris Data (a s3-compatible provider), and thus even Railway reaches out to it via the internet.
3 months ago
If you have any more problems, feel free to create another help thread!
Status changed to Solved passos • 3 months ago