Supabase IPv4 Deprecation Can Lead to Connection Errors
grooney opened this issue · comments
I realize that this may be more of documentation improvement request but wanted to flag as a bug in case others bumped into it - Supabase's recent migration to IPv6 caused connection errors with this sync.
My ECS Task started reporting the following error:
connect ENETUNREACH
when trying to connect to the database.
I had to switch to using the pooling URI (containing @[aws-region].pooler.supabase.com:[port]/postgres)vs the direct connection URL provided in the documentation. Not entirely sure if that's proper solve as it may drain available pool connections, but resolved the issue for now. Is this the recommended solve for this error?