Calls to Supabase Data API calls are indefinitely hung without error
Database shared pooler logs show "DbHandler: Connection failed {:error, :econnrefused} " messages.
We're unable to make Supabase data API calls from any of our servers.
Any suggestions for troubleshooting the issue?
17 Replies
Was it working at one point?
Check the status of your instance.
Check the usage info for CPU/Memory/connections.
it was working as of couple hours ago. Then we started seeing the indefinite hang on our servers and also locally run server, from 5:42pm CT to 6:44pm.
Now we're seeing normal operation on a local server after a server restart.
The web servers are still hung when making calls to Supabase. Might have to restart them I think, because that seemed to help withthe local server.
Thanks for the input. How would I check the status of my instance?
No one else reporting anything here or github.
Home page upper right has status. Usage is in settings.
You say web servers are you using direct DB connections or the REST API?
Project status shows everything as healthy.
We're using the rest API
You checked DB connections tag which is supposed to be direct connections.
But not clear I guess..
You do say DB pooler though
my bad, fixed it
correct, we use DB pooler
That is not the REST API.
That is either supavisor or pgbouncer.
Are you Pro?
If so make sure you are using pgbouncer.
yes, we're on the Team plan
Make sure you already started a support request then.
The logs show "Elixir.Supavisor.DbHandler", so I'm guessing Supavisor
Yes.
You should be using pgbouncer if you need a pooler.
Well I guess if you are limited to IPv4 then that would not help...
But it gets you off of the shared community pooler to your own dedicated pooler.
How would we specify the pooler type? we're using the 'pg' typescript package
Still not other reports of outage and status page is good... So may just be your instance or a supavisor node.
I don't have a Pro plan so don't know if the connect tab shows you the PGbouncer url or not. It is the recommended way to go for pooling for Pro though now.
https://supabase.com/docs/guides/troubleshooting/how-do-i-update-connection-pool-settings-in-my-dashboard-wAxTJ_
thanks. I've created a support ticket. Will update here upon resolution of the issue.
will look into pgbouncer.
I'm a little confused here as you mention data api, rest API and then DB pooler. I think you should make certain of which you are having an issue with before reporting to Supabase support as they will be equally as confused as us on here without this being made clear.
My bad on the confusion caused. We use DB pooler on the servers where we're seeing the indefinite hang. We use the Rest API on the clientside and that seems to be working fine.
Issue resolution: A Supabase support agent explained that a connection disruption occurred because the database’s fail2ban security system mistakenly identified the shared pooler as a potential attacker. This resulted in the pooler being banned from connecting for one hour. They recommended using direct connections or a dedicated pooler to avoid further disruptions until the shared pooler problem is resolved.
Thanks for coming back with an update on this.