# Cannot deploy app since yesterday **URL:** \ **Category:** General\ **Tags:** login-only\ **Created:** [August 8, 2023, 2:21pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676 "2023-08-08T14:21:33Z")\ **Posts on this page:** 16\ **Page:** 1
**Author:** ![wobbleburger](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/wobbleburger/32/13777_2.png) [@wobbleburger](https://community.fly.io/u/wobbleburger)\ **Post date:** [August 8, 2023, 2:21pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/1 "2023-08-08T14:21:33Z")
I’m trying to deploy my app but it keeps hanging and then timing out with this error: [1/4] Waiting for 91857597a96483 [worker] to have state: started Error: timeout reached waiting for machine to started failed to wait for VM 91857597a96483 in started state: Get “[https://api.machines.dev/v1/apps/\*\*\*\*\*/machines/91857597a96483/wait?instance\_id=01H7AQYFWCY8MXT8115ZDS11V3&state=started&timeout=60](https://api.machines.dev/v1/apps/ ***** /machines/91857597a96483/wait?instance_id=01H7AQYFWCY8MXT8115ZDS11V3&state=started&timeout=60)”: net/http: request canceled note: you can change this timeout with the --wait-timeout flag This problem started yesterday. On the monitoring logs screen on the dashboard it’s hanging at this line: 2023-08-08T14:23:51.869 runner[91857597a96483] sjc [info] Configuring firecracker ---
**Author:** ![carldr](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/carldr/32/14388_2.png) [@carldr](https://community.fly.io/u/carldr)\ **Post date:** [August 8, 2023, 5:11pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/2 "2023-08-08T17:11:15Z")
I’ve been getting the same all day - trying to deploy into ams. I finally got deploying to work by destroying all of my standby machines, and making sure all of the auto-scaling machines had started. But then trying to deploy again results in the same : 2023-08-08T17:27:51.569 runner[148e270a3562e8] ams [info] Successfully prepared image [registry.fly.io/\*\*\*\*\*:deployment-01H7B30NSN0RY3XQMBA22TER13](http://registry.fly.io/ ***** :deployment-01H7B30NSN0RY3XQMBA22TER13) (10.70389854s) 2023-08-08T17:27:51.940 runner[148e270a3562e8] ams [info] Configuring firecracker ---
**Author:** ![zace](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/zace/32/14390_2.png) [@zace](https://community.fly.io/u/zace)\ **Post date:** [August 8, 2023, 8:10pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/3 "2023-08-08T20:10:35Z")
Same issue, just started last night for us. ```auto Updating existing machines in ' ****' with rolling strategy [1/4] Waiting for 683dde2a77e618 [worker] to have state: started Error: timeout reached waiting for machine to started failed to wait for VM 683dde2a77e618 in started state: Get "https://api.machines.dev/v1/apps/ **** /machines/683dde2a77e618/wait?instance_id=01H7BBZKNQKS8NY24X0S177FVT&state=started&timeout=60": net/http: request canceled note: you can change this timeout with the --wait-timeout flag ``` ---
**Author:** ![paulwvnjohi](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/paulwvnjohi/32/44340_2.png) [@paulwvnjohi](https://community.fly.io/u/paulwvnjohi)\ **Post date:** [August 8, 2023, 9:30pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/4 "2023-08-08T21:30:38Z")
same here ☹ ---
**Author:** ![wobbleburger](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/wobbleburger/32/13777_2.png) [@wobbleburger](https://community.fly.io/u/wobbleburger)\ **Post date:** [August 8, 2023, 9:39pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/5 "2023-08-08T21:39:29Z")
I resolved this by destroying the machine that got stuck, and then redeploying. ---
**Author:** ![paulwvnjohi](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/paulwvnjohi/32/44340_2.png) [@paulwvnjohi](https://community.fly.io/u/paulwvnjohi)\ **Post date:** [August 8, 2023, 9:40pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/6 "2023-08-08T21:40:45Z")
restarting the specific machine that froze also works ---
**Author:** ![Quintessa](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/quintessa/32/13606_2.png) [@Quintessa](https://community.fly.io/u/Quintessa)\ **Post date:** [August 8, 2023, 9:42pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/7 "2023-08-08T21:42:13Z")
London: Error: failed to fetch an image or build from source: error rendering push status stream: received unexpected HTTP status: 500 Internal Server Error ---
**Author:** ![billyz](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/billyz/32/14396_2.png) [@billyz](https://community.fly.io/u/billyz)\ **Post date:** [August 9, 2023, 2:13am UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/8 "2023-08-09T02:13:47Z")
I’m brand new. I think I’m experiencing the same issue. I was able to redeploy by destroying all machines. But the issue returns each time I try to deploy. It’s always the sidekiq one. With the message “Waiting for XXXX [sidekiq] to have state: started” I’ll see if I can figure out how to restart that one machine as someone suggested above. ---
**Author:** ![BoHakio](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/bohakio/32/14398_2.png) [@BoHakio](https://community.fly.io/u/BoHakio)\ **Post date:** [August 9, 2023, 7:35am UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/9 "2023-08-09T07:35:55Z")
I have the same issue like you. Mine also stops at deploying sidekiq app ---
**Author:** ![carldr](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/carldr/32/14388_2.png) [@carldr](https://community.fly.io/u/carldr)\ **Post date:** [August 9, 2023, 7:49am UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/10 "2023-08-09T07:49:19Z")
Still happening for me this morning. Starting or restarting the “stuck” app doesn’t help (I have 8 machines across 4 processes, I’ve tried doing that with all of them.) I’m going to sign up to the Starter plan and try their email support and see if the support is better there - this is my first month running something live with Fly, it’ll be a real shame to have to move elsewhere, but not being able to deploy for 24 hours is kinda a blocker … ---
**Author:** ![carldr](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/carldr/32/14388_2.png) [@carldr](https://community.fly.io/u/carldr)\ **Post date:** [August 9, 2023, 1:41pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/11 "2023-08-09T13:41:13Z")
Stttttttttil can’t deploy. And no reply from support. `fly deploy --strategy immediate` does seem to work - although be sure about what you’re deploying. ---
**Author:** ![paulwvnjohi](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/paulwvnjohi/32/44340_2.png) [@paulwvnjohi](https://community.fly.io/u/paulwvnjohi)\ **Post date:** [August 9, 2023, 2:26pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/12 "2023-08-09T14:26:07Z")
been religiously following this thread 🙂 ---
**Author:** ![wjordan](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/wjordan/32/1280_2.png) [@wjordan](https://community.fly.io/u/wjordan)\ **Post date:** [August 9, 2023, 6:45pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/13 "2023-08-09T18:45:52Z")
Hi all, we identified a bug in `fly deploy` introduced a couple days ago (starting in v0.1.72) causing deploys to incorrectly wait on an app’s [standby machines](https://fly.io/docs/reference/app-availability/#standby-machines-for-process-groups-without-services) to enter the `started` state (which will never happen, resulting in a timeout error), when they should properly be skipped. ~~We are working on publishing a new release with a fix (which will be v0.1.74).~~ A new version of flyctl (v0.1.74) has been released with a fix for this issue. In the meantime, you can manually downgrade to v0.1.71 (after disabling [autoupdate](https://community.fly.io/t/flyctl-versions-autoupdating-and-the-cli-apocalypse/13794) first) to work around this issue: ```auto flyctl settings autoupdate disable curl -L https://fly.io/install.sh | sh -s -- v0.1.71 ``` Sorry for the inconvenience! I hope this resolves your issues. ---
**Author:** ![wjordan](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/wjordan/32/1280_2.png) [@wjordan](https://community.fly.io/u/wjordan)\ **Post date:** [August 9, 2023, 6:58pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/14 "2023-08-09T18:58:44Z")
We just released flyctl [v0.1.74](https://github.com/superfly/flyctl/releases/tag/v0.1.74) with a fix for this issue. Flyctl will update automatically, or run `fly version upgrade` to upgrade manually. ---
**Author:** ![carldr](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/carldr/32/14388_2.png) [@carldr](https://community.fly.io/u/carldr)\ **Post date:** [August 9, 2023, 7:32pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/15 "2023-08-09T19:32:09Z")
Thanks for your reply, I’ll try it out. ---
**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\ **Post date:** [August 16, 2023, 7:32pm UTC](https://community.fly.io/t/cannot-deploy-app-since-yesterday/14676/16 "2023-08-16T19:32:57Z")
Closed on August 16, 2023, 7:32pm UTC This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.