flyctl deploy
machine restart policy set to ‘no’, not restarting - error.
document's solution -> fly machine update --restart always <machine-id>
but deploy error already destroy the machine.
so the documents solution is useless.
next ‘flyctl deploy’ create new machine.
but because it is not set to ‘–restart always’, error occur again.
any prior to error configuration is not possible?
Hi @hanasiu
This issue might not be related to the restart policy. Were there any other error messages before or after the restart policy error? Try posting all the output from the failed fly deploy command, as well as the logs from that time period.
thank you for response. I tried and failed continuously. so I go to other flatform.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.