Question about custom domain and t3.storage.dev

Questions / Help
1

I see you guys are now suggesting to use t3.storage.dev as the endpoint for anything that doesn’t run inside the Fly network. I have users all around the world accessing my buckets using a custom domain. These custom domains were set with the suggested CNAME which seems to point to fly.storage.tigris.dev which according to the new UI, is the endpoint optimized for Fly Apps.

So… how I can use the Default endpoint for high performance across all cloud providers and regions when using a custom domain? Or is that not possible? Should I switch to using the new t3.storage.dev endpoint instead of my custom domain if I want to take advantage of this high performance?

2

Great question!

You’re right — fly.storage.tigris.dev is optimized for apps running inside Fly for the best possible performance globally within that environment.

The t3.storage.dev endpoint is designed for globally distributed access and works best for apps or users outside the Fly network. If you’re using a custom domain and think you will benefit more from using the t3.storage.dev domain, you can point your CNAME to t3.storage.dev instead.

3

This doesn’t seem to work.

When switching my CNAME from sub.mydomain.com.fly.storage.tigris.dev to sub.mydomain.com.t3.storage.dev I get an SSL error when accessing any file via https://sub.mydomain.com/path/to/file

Chrome shows net::ERR_CERT_COMMON_NAME_INVALID

4

Could you revert the change in the meantime? We will take a look at it.

5

I’ve already did as soon as I noticed the issue. Please let me know once it’s fixed. Thanks.

6

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.