Connection timeout, unable to to ping db.mkrdytbwipfmzroshpfh.supabase.co
pg_isready -h db.mkrdytbwipfmzroshpfh.supabase.co -p 5432 -U postgresdb.mkrdytbwipfmzroshpfh.supabase.co:5432 - no response
pg_isready -h db.mkrdytbwipfmzroshpfh.supabase.co -p 5432 -U postgresdb.mkrdytbwipfmzroshpfh.supabase.co:5432 - no response
pg_isready -h 2406:da14:271:9904:a2f4:2874:5e7b:a29 -p 5432 -U postgres2406:da14:271:9904:a2f4:2874:5e7b:a29:5432 - no response
pg_isready -h 2406:da14:271:9904:a2f4:2874:5e7b:a29 -p 5432 -U postgres2406:da14:271:9904:a2f4:2874:5e7b:a29:5432 - no response
Connection terminated due to connection timeout at /root/backend/node_modules/pg-pool/index.js:45:11 at processTicksAndRejections (node:internal/process/task_queues:105:5)
Connection terminated due to connection timeout at /root/backend/node_modules/pg-pool/index.js:45:11 at processTicksAndRejections (node:internal/process/task_queues:105:5)
ping db.mkrdytbwipfmzroshpfh.supabase.coPING db.mkrdytbwipfmzroshpfh.supabase.co (2406:da14:271:9904:a2f4:2874:5e7b:a29) 56 data bytes... no reponse
ping db.mkrdytbwipfmzroshpfh.supabase.coPING db.mkrdytbwipfmzroshpfh.supabase.co (2406:da14:271:9904:a2f4:2874:5e7b:a29) 56 data bytes... no reponse
Checked dashboard, no IP bans, no IP restrictions. Suddenly failed to connect from server, no Firewall block. Local machine connection ok.
Supabase gives you the tools, documentation, and community that makes managing databases, authentication, and backend infrastructure a lot less overwhelming.
