"No deployment available to monitor" when deploying node.js app

I have been running into issues deploying my fly.io app all week. Here’s the complete output from trying to deploy it. I am able to run it locally with “node server.js” no problem. I have seen other people mention a similar issue recently but have not been able to get any of the solutions to work.

$ flyctl deploy
==> Verifying app config
→ Verified app config
==> Building image
Remote builder myappname ready
==> Building image with Buildpacks
→ docker host: 20.10.12 linux x86_64
20: Pulling from heroku/buildpacks
Digest: sha256:etcetc1
Status: Image is up to date for heroku/buildpacks:20
20-cnb: Pulling from heroku/heroku
Digest: sha256:etcetc2
Status: Image is up to date for heroku/heroku:20-cnb
heroku/nodejs-engine 0.8.14
heroku/nodejs-npm 0.5.2
heroku/procfile 2.0.0
Restoring metadata for “heroku/nodejs-engine:dist” from app image
Restoring metadata for “heroku/nodejs-engine:web_env” from app image
Restoring metadata for “heroku/nodejs-npm:toolbox” from cache
Restoring data for “heroku/nodejs-engine:dist” from cache
Restoring data for “heroku/nodejs-npm:toolbox” from cache

[Heroku Node.js Engine Buildpack]

[Checking Node.js version]
Detected Node.js version range: 16.17.1
Resolved Node.js version: 16.17.1

[Installing Node.js distribution]
Reusing Node.js 16.17.1
[INFO] Installing toolbox
[INFO] Using npm v8.15.0 from Node
[INFO] Installing node modules from ./package-lock.json
npm WARN config production Use --omit=dev instead.
npm WARN deprecated w3c-hr-time@1.0.2: Use your platform’s native performance.now() and performance.timeOrigin.
npm WARN deprecated rollup-plugin-terser@7.0.2: This package has been deprecated and is no longer maintained. Please use @rollup/plugin-terser
npm WARN deprecated sourcemap-codec@1.4.8: Please use @jridgewell/sourcemap-codec instead
npm WARN deprecated uuid@3.4.0: Please upgrade to version 7 or higher. Older versions may use Math.random() in certain circumstances, which is known to be problematic. See There’s Math.random(), and then there’s Math.random() · V8 for details.
npm WARN deprecated querystring@0.2.0: The querystring API is considered Legacy. new code should use the URLSearchParams API instead.
npm WARN deprecated request@2.88.2: request has been deprecated, see Request’s Past, Present and Future · Issue #3142 · request/request · GitHub
npm WARN deprecated har-validator@5.1.5: this library is no longer supported
npm WARN deprecated formidable@1.2.6: Please upgrade to latest, formidable@v2 or formidable@v3! Check these notes: formidable/VERSION_NOTES.md at master · node-formidable/formidable · GitHub
npm WARN deprecated @babel/polyfill@7.12.1: :rotating_light: This package has been deprecated in favor of separate inclusion of a polyfill and regenerator-runtime (when needed). See the @babel/polyfill docs (@babel/polyfill · Babel) for more information.
npm WARN deprecated core-js@2.6.12: core-js@<3.23.3 is no longer maintained and not recommended for usage due to the number of issues. Because of the V8 engine whims, feature detection in old core-js versions could cause a slowdown up to 100x even if nothing is polyfilled. Some versions have web compatibility issues. Please, upgrade your dependencies to the actual version of core-js.

added 985 packages, and audited 986 packages in 23s

160 packages are looking for funding
run npm fund for details

6 vulnerabilities (4 moderate, 2 critical)

To address issues that do not require attention, run:
npm audit fix

To address all issues possible (including breaking changes), run:
npm audit fix --force

Some issues need review, and may require choosing
a different dependency.

Run npm audit for details.
npm notice
npm notice New major version of npm available! 8.15.0 → 9.4.0
npm notice Changelog: https://github.com/npm/cli/releases/tag/v9.4.0
npm notice Run npm install -g npm@9.4.0 to update!
npm notice

[Warning: Skip pruning because NODE_ENV is not ‘production’.]

[Discovering process types]
Procfile declares types → web, heroku
Reusing layer ‘heroku/nodejs-engine:dist’
Reusing layer ‘heroku/nodejs-engine:web_env’
Adding 1/1 app layer(s)
Reusing layer ‘launcher’
Reusing layer ‘config’
Reusing layer ‘process-types’
Adding label ‘io.buildpacks.lifecycle.metadata’
Adding label ‘io.buildpacks.build.metadata’
Adding label ‘io.buildpacks.project.metadata’
Setting default process type ‘web’
Saving registry.fly.io/veyerollfly:cache
*** Images (54d9bbb2399d):
Reusing cache layer ‘heroku/nodejs-engine:dist’
Adding cache layer ‘heroku/nodejs-npm:node_modules’
Reusing cache layer ‘heroku/nodejs-npm:toolbox’
→ Building image done
==> Pushing image to fly
The push refers to repository [registry.fly.io/veyerollfly]
[layers exist/are pushed]
deployment-xxxx: digest: sha256:xxxxx size: 2623
→ Pushing image done
image: registry.fly.io/myappname:deployment-xxxxx
image size: 905 MB
==> Creating release
→ release v65 created

→ You can detach the terminal anytime without stopping the deployment
==> Monitoring deployment
Logs: Sign In · Fly
Error 1 error occurred:

  • No deployment available to monitor
1 Like

Check fly scale show to make sure your app hasn’t been scaled to zero at some point, that’s a common reason for deployments not proceeding as expected. If it is zero you can run fly scale count 1 to set a single instance.

1 Like

Ah, that was it. Forgot I had scaled it to zero to pause it before. Thanks.