Direct Database Connection Refusing Port 5432 After Working Yesterday
What I'm trying to achieve:
Connect to my Supabase database using direct database access (my account has the ipv4 add-on) through a Docker container running Letta/MemGPT.
What's going wrong:
Connection was working perfectly yesterday, but today getting "Connection refused" on port 5432. The database host IP appears to be completely unreachable.
Environment details:
- OS: Ubuntu 24.04 (WSL2)
- Platform: Docker container
- Database driver: pg8000 (PostgreSQL)
- Project ID: pvxhhmwxdcsvlqouptuc
- Database host: db.pvxhhmwxdcsvlqouptuc.supabase.co (resolves to 15.157.30.159)
Error:
Troubleshooting completed:
- Verified no configuration changes on my end
- Confirmed direct database access is enabled in dashboard
- Checked Supabase status page (no outages)
- Network tests show 100% packet loss to the IP address
- DNS resolution works correctly
Connection string format:
Could this be related to infrastructure changes on the Supabase side? The IP seems completely unreachable from multiple network tests.
Any guidance would be appreciated!
Connect to my Supabase database using direct database access (my account has the ipv4 add-on) through a Docker container running Letta/MemGPT.
What's going wrong:
Connection was working perfectly yesterday, but today getting "Connection refused" on port 5432. The database host IP appears to be completely unreachable.
Environment details:
- OS: Ubuntu 24.04 (WSL2)
- Platform: Docker container
- Database driver: pg8000 (PostgreSQL)
- Project ID: pvxhhmwxdcsvlqouptuc
- Database host: db.pvxhhmwxdcsvlqouptuc.supabase.co (resolves to 15.157.30.159)
Error:
Troubleshooting completed:
- Verified no configuration changes on my end
- Confirmed direct database access is enabled in dashboard
- Checked Supabase status page (no outages)
- Network tests show 100% packet loss to the IP address
- DNS resolution works correctly
Connection string format:
postgresql://postgres:PASSWORD@db.pvxhhmwxdcsvlqouptuc.supabase.co:5432/postgresCould this be related to infrastructure changes on the Supabase side? The IP seems completely unreachable from multiple network tests.
Any guidance would be appreciated!
