5 hours ago
Running a small VM that has just started getting errors in the last 48 hrs. Here is a sample from the logs:
"message": " Error: connect ETIMEDOUT 54.153.234.207:5432",
"message": " syscall: 'connect',",
"message": " address: '54.153.234.207',",
"message": " port: 5432",
"message": " },",
"message": " Error: connect ENETUNREACH 2406:da1c:b7c:d0e:9858:9714:c422:b17b:5432 - Local (:::0)",
"message": " at ignore-listed frames {",
"message": " errno: -101,",
"message": " code: 'ENETUNREACH',",
"message": " syscall: 'connect',",I can't tell if this is trying to connect to the database (Neon) or something inside Railway.
How do I fix this issue? Do I need to deploy a larger VM?
Any help much appreciated!
Regards,
Michael
3 Replies
5 hours ago
This thread has been opened as a bounty so the community can help solve it.
Status changed to Open Railway • about 5 hours ago
5 hours ago
54.153.234.207 is an AWS IP and I believe Neon runs primarily on AWS, I could be wrong though but worth looking into that. Can you reach your Neon database from your local machine?
regarding ENETUNREACH 2406:da1c:b7c:d0e:9858:9714:c422:b17b:5432, can you try enabling outbound IPv6 in your service settings?
And no a container with more resources won't solve this, this seems scoped to being a networking issue
dev
54.153.234.207 is an AWS IP and I believe Neon runs primarily on AWS, I could be wrong though but worth looking into that. Can you reach your Neon database from your local machine? regarding `ENETUNREACH 2406:da1c:b7c:d0e:9858:9714:c422:b17b:5432`, can you try enabling outbound IPv6 in your service settings? And no a container with more resources won't solve this, this seems scoped to being a networking issue
4 hours ago
Thanks for the fast reply! Yes I can access the Neon database without issue. I am redeploying now with IPv6 switched on, so I will see how that goes. Good to know this is not about capacity. Thanks!