supabase error: connect ENETUNREACH
aljorgeviHOBBY
2 months ago
## SSL Handshake Timeout with Supabase Connection
### Description of the issue
I'm experiencing persistent connection errors between my Strapi application (deployed on Railway) and my Supabase PostgreSQL database. The application fails to start with ENETUNREACH errors.
### Error messages
```
Error: connect ENETUNREACH 2a05:d014:1c06:5f03:c932:5160:1e02:be08:5432 - Local (:::0)
at internalConnect (node:net:1094:16)
at defaultTriggerAsyncIdScope (node:internal/async_hooks:464:18)
at GetAddrInfoReqWrap.emitLookup [as callback] (node:net:1493:9)
at GetAddrInfoReqWrap.onlookupall [as oncomplete] (node:dns:132:8)
```
### Environment Details
- **Platform**: Railway
- **Framework**: Strapi
- **Database**: Supabase PostgreSQL
- **Connection Configuration**:
- Database Host: db.rduqbybrqjzutyzxjosq.supabase.co
- Database Port: 5432
- SSL: false
### What I've Tried
- Setting DATABASE_SSL to false
- The application works perfectly in development environment
- The error seems to be related to IPv6 connectivity issues
### Questions
1. Is this a known issue with Railway's networking when connecting to Supabase?
2. Are there any specific environment variables or configuration settings I should modify to resolve this IPv6/networking issue?
3. Should I be using a different SSL configuration for production deployment?
Any help or guidance would be greatly appreciated. Thank you!
1 Replies
2 months ago
Hello,
Railway does not support outbound connects to IPv6 only networks, you will need to connect to Supabase via a domain that returns an IPv4 address.
Best,
Brody
Status changed to Awaiting User Response railway[bot] • 2 months ago