Deploy continously fail due to timeout

1st deploy - failed
image

machine ended up in suspended state had to delete it,

2nd deploy - failed
image

3rd deploy - failed
image

I am at the end of my wits and patience now

the machine never starts and the Checking DNS configuration never goes through. I have even set restart policy to always in the toml as well. whats the resolution to this loop ?

machine is in suspended state, how to get it out of it
image

state is created

event on the machine stuck at launch

is this SIN region having issue or fly is having issues that will eventually get acknowledged at some point ?

moved to LAX region and deploys went through, there seems to be some issue in SIN. Like all issues fly will eventually acknowledge it but it that the response as a platform one needs to align on ? Not really giving confidence of running production workloads

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.