Error: failed to connect to fly machine: Supposedly started, and not stopped

[ignoramous]

Thank you.

@eli

…our launch plan might help ease any hiccups you hit throughout the process.

I do plan to take it up once we build some confidence in how we’d operate the service with Fly Machines.

@eli

I’d guess that your app was more susceptible to this problem because of the number of machines in use and the way that they’re distributed across regions.

Hm, could this issue-- I recently deployed udns, a Machine app, with flyctl to all available Fly regions, and found that, one VM is spun-up per connection instead of the connection being sent to an already alive VM (link)-- that we encountered be related?