Pooler Error ClientHandler: socket closed with reason

[SayonB]

All connections to my database is failing with the error "SSL connection has been closed unexpectedly"

When I go to https://supabase.com/dashboard/project/[PROJECT_ID]/logs/pooler-logs I see many logs with

ClientHandler: socket closed with reason {:shutdown, :terminate_received}, DbHandler {#PID<50015.13801.5652>, {:error, {:exit, {:timeout, {:partisan_gen_statem, :call, [#PID<50015.13801.5652>, :get_state_and_mode, 5000]}}}}}

and

ClientHandler: socket closed with reason {:shutdown, :terminate_received}

we've tried restarting supabase cloud, upgrading it, removing SSL enforcing. What else can we do?

[GaryAustin1]

Please report this to support.

[IgnacioVegaMx]

I already reported it

[IgnacioVegaMx]

If the same thing happens to me, connecting from pgAdmin4 and PHP, any ideas on this?

The most curious thing is that it only happens to me in the project that is in the Pro plan, I have two others and I can access those, is it a matter of the Pro plan projects?

[GaryAustin1]

I doubt it is Pro plan, but more likely a specific supavisor server if that is the issue.
Also if you support ipv6 you can use the direct port and that is working for at least one user as a non-pooler need work around.

[groksrc]

I am having the same problem. We have opened a ticket.

[GaryAustin1]

https://status.supabase.com/incidents/h5t5p6y0jxvc

[AlanChen4]

I'm using the Supabase connection pooler and was able to resolve this by increasing the Pool Size (Settings > Database > Connection Pooling Configuration). Default value for me was 15, and stopped having this issue after increasing to 48.

[quantchain14]

fuck sake you saved me

[peterlendtech503]

you saved me here Alan!