Can't use t3.storage.dev with custom domain

,
1

Tried changing my CNAME record from my.custom.domain.fly.storage.tigris.dev. to my.custom.domain.t3.storage.dev. but it still doesn’t work. Chrome shows net::ERR_CERT_COMMON_NAME_INVALID when trying to access an asset.

I have a lot of references to assets using my custom domain so I’d prefer to switch to t3.storage.dev by just changing the CNAME record instead of changing all the URLs.

Most of the assets are requested browser-side by users from all around the world, so I definitely want to use t3.storage.dev.

Please address this. I’ve sent out 2 emails already to help@tigrisdata.com and got no response. I’m spending over $60/mo on just Tigris, so please have a look at this.

Thank you

3

Please continue using the fly.storage.tigris.dev domain with your custom domain. Are you running into any issues with the current setup?

4

Some users report difficulties in fetching certain files, particularly when a file is uploaded from my server in the US and a user in Asia attempts to access it almost immediately. There seems to be a delay in these cases, which I have also experienced at times.

I prefer not to use the fly.storage.tigris.dev domain if it is intended for use within the Fly network, as 90% of the requests to the storage come from outside.

Could someone clarify the actual difference between the two domains? If using t3.storage.dev is genuinely advantageous for my situation, I will update all the URLs to use it instead of my custom domain.

5

@empz when you see the delay, do you mean you see 404, or do you mean you see high latency for the first request?

fly.storage.tigris.dev is optimized for Fly apps which is why we recommend for anyone building with or using Tigris within their apps.

We launched our new endpoint t3.storage.dev for two reasons:

  1. We have lot of users who are not on Fly
  2. Fly machines and edge have limitations on network bandwidth, and it was affecting the performance of our high scale customers