Supabase Storage → Tigris Issue, "No Such Host"

I'm looking to move from the S3 compatible Supabase Storage to Tigris Data, but am seeing this error from Tigris' “Enable Data Migration” feature in the web UI:

Get "https://[supabase_bucket_name].[supabase_project_reference_id].co/storage/v1/s3?delimiter=&list-type=2&max-keys=1&prefix=" : dial tcp: lookup [supabase_bucket_name].[supabase_project_reference_id].supabase.co on [fdaa::3]:53: no such host

Screenshot of set‑up in the UI:

! CleanShot 2024-10-10 at 14.39.16

I have no issues accessing the Supabase Storage bucket using the S3 credentials via Cyber/Mountain Duck and also using the higher‑level credentials via Supabase’s Python library.

What have I missed?

Hey,

Thanks for reporting!

There are two errors in the EU region from last night indicating an issue with the endpoint configuration that may have escalated into this error. The error there indicated that https://``https:// was missing from the endpoint definition. We will add validation to the UI to ensure this requirement is clear in the future.

Could you email the details on what bucket might be affected to help@tigrisdata.com? I want to make sure that the error that we spotted is for your bucket and endpoint. Thanks!

Great, thanks for getting back to me; will email now.

Continue the conversation

Join the Discord to ask follow-up questions and connect with the community

Tigris

All things Tigris: the Globally Distributed S3-Compatible Object Storage.

220 Members

Join