I keep getting this issue:
connect ETIMEDOUT
Not related but about 2 weeks we have been suffering with issues in fork volumes and database (legacy). We are considering into paying fly.io support but these issues keeps stacking that like below:
Error: failed to launch VM: internal: could not claim volume for machine: volume is not mountable, unable to claim (Request ID: 01JWRGR2A3GFC0JN91DQH89NE5-lax)
Fly.io is great at ease of use, but getting good feedback about the service it’s almost impossible. The hidden cost of our engineering hours to work around their issues has been probably higher than looking at other services which requires more upfront but at least we have way more control.
That’s not a database connection problem. That’s a fly.io volume problem. Huge difference. Please find the appropriate forum for the fly.io volume problem. Thanks.
1 Like
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.