I’m currently unable to deploy an app because during the deployment, I see the following error:
Failed to update machines: failed to update machine __machine_id__: failed to destroy VM __machine_id__: not_found: machine not found
If I try to destroy the machine via flyctl (or run any other command on it), I get:
Error: machine __machine_id__ was not found in app '__app_name__'
I tried to --force
destroy the machine as well. Is there anything else I can try to either remove or regain control of this machine?
Thanks!
halfer
June 24, 2025, 10:34pm
2
Are you able to shell into the machine?
This is an Elixir app, so I can remote console in via
fly ssh console --config fly.toml --pty -C "/app/bin/<myapp> remote"
But, there are multiple machines and I’m assuming this isn’t going to hit the machine that’s not responding.
halfer
June 24, 2025, 11:01pm
4
Ah, yes, I meant that you should try flyctl ssh console --machine ...
. If that doesn’t work, try the account support email . Someone will blat your machine for you.
Thanks for the tip. I’m getting:
Error: --machine="__machine_id__" not found/started
Is there any other way to get them to address my machine, without purchasing a support package?
I’m also seeing “These Machines’ hosts could not be reached.” when I list the machines.
rowboat
ID NAME STATE CHECKS REGION ROLE IMAGE IP ADDRESS VOLUME CREATED LAST UPDATED PROCESS GROUP SIZE
__machine_id__* machine-name-XXXX stopped sea
...
* These Machines' hosts could not be reached.
halfer
June 25, 2025, 12:08am
7
Use the link I’ve specified; that’s account support, not paid support. It’s free of charge.
Thanks, that link goes to Support · Fly Docs for me, which specifies that I need a support plan to email support. But maybe I’m missing something?
Yep, the link has an anchor (#
) that jumps down to the “Billing and account support” section…
Who can use this: Everyone
Use this for: Billing and account management issues.
For questions about a specific invoice or account management issues, you can email us at billing@fly.io .
(Some browsers ignore those, though, and just leave you hanging unknowingly at the top of the page.)
If that doesn’t pan out, people have had luck with fly deploy --exclude-machines=<machine-id>
in the past.
Aside: Also try checking your dashboard for a message about a failed underlying physical host machine; that’s the usual reason for “could not be reached”.
1 Like
system
Closed
July 2, 2025, 12:51am
10
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.