Troubleshooting deployments

Start on the deployment's page. Why it failed is under the header, in red, with the service's name first. That service's tab has its Build and Deploy logs. See Deployments.

My build failed

Build failed. web: …

The deployment stopped before it changed anything, so your old version keeps running. Open the service's Build log and read the end of it: the failing step is there. Troubleshooting builds covers the common causes.

My new version never becomes healthy

container … failed health monitoring: running (health: unhealthy), or ending in timed out

A new replica didn't answer its Healthcheck path in time. Ployz stopped it and kept the old version serving. A running service that fails its health check shows Unhealthy.

Listen on PORT. The health check calls the PORT variable, 8080 unless you set it. Make your app listen on it, or set PORT under Variables to the port it uses.
Listen on 0.0.0.0, not 127.0.0.1. See My app shows 502 Bad Gateway.
Answer with a 2xx status, not a redirect to https:// or /login. See Deployments.
Give it time to boot. If you lowered Healthcheck timeout under Settings → Deploy, raise it. Otherwise make your app start faster.

My app exits as soon as it starts

container … failed health monitoring: exited with code 1, or ending in restarting

The new replica stopped right after it started, and the old version kept running. Any exit code can show here.

Read the Deploy log for the error your app printed before it stopped.
Check the service's Variables for one your app needs that's missing or wrong.
Fix the Start command, or clear it to run the image's own command.
Code 137 usually means the replica went over its Memory limit. Raise or clear it under Settings → Scale.

A service waits on another that never comes up

dependency … failed health gate

This service references another in its variables, and that one didn't come up healthy, so Ployz didn't start this one. Fix the service the message names first; its Logs say why.

My pre-deploy command failed

hook container … failed: exited with code 1, or failed: timed out

None of the service's replicas were replaced, so the old version keeps running.

Read the Deploy log: the command's output is there.
timed out means it ran longer than 5 minutes. Make it faster, or run the slow part outside the deploy.
To try the command in a running replica, use the CLI (CLI-only for now):
```
ployz exec api npm run migrate
```

My service shows Crashed or Stopped

None of the service's replicas is running. Crashed means one exited with an error or keeps restarting; Stopped means they all exited cleanly and weren't restarted. During a first deploy a card can read Not running or Crashed for a few seconds: if the deployment ends Deployed, there's nothing to fix.

Read the last lines in the service's Logs. If they end with no error, it may have run out of memory: raise Memory limit.
A start command that finishes, instead of running a server, restarts over and over or stops. Set Start command to the command that runs your app.
If it stopped because of something outside your app, like a database that was down, restart it. That's CLI-only for now:
```
ployz service restart api
```

My deployment stays Queued

Another deployment of the environment is running. Yours runs after it; cancel that one from Deployments if it's stuck.
It's building on GitHub Actions, and the run hasn't started or finished. Its Build log shows where it is.
The bottom bar shows Add a server: your organization has no server yet. Add one.
Nothing else is running: click Deploy now on the deployment's page.

My push didn't deploy

Auto-deploy is off under Settings → Source, or the push went to another Git branch.
Watch paths are set and the push changed none of those files.
Wait for CI is on and a check failed, or no checks ran. Re-run the check on GitHub, or push again.
The repository is public and connected without the Ployz GitHub App. See Deploy a public repository without the app.
Your organization has no servers. Add one.

My new image didn't deploy

Pushing an image to your registry deploys nothing, and a server that already has a tag, like latest, keeps its copy. Give each release its own tag and change Container image to it. See Ship a new version of your image.

Deploy says a service has nothing to run

api has nothing to run yet: add an image or connect a repository

The service has no source, and its card shows No source. Ployz won't deploy the environment until it has one. Open its Settings → Source and click Git repository or Container image, or delete the service.

My uploaded code is gone

api has no source to build: its last upload is gone and no image is left to reuse. Upload it again or add an image.

Run ployz up again from your app's directory, or click Add an image to api on the deployment's page.

Deploy asks me to confirm it deletes data

Deploy deletes data

This deploy would delete a volume's data: a volume you deleted, or a database service, which takes its volume with it.

If you meant it, type your project/environment and click Deploy.
If you didn't, cancel, then open Details in the bottom bar and click Discard beside the volume or service.

My services show Can't reach servers

Can't reach servers

Ployz can't reach your servers, so it can't deploy to them or read their logs. See Troubleshooting servers. Once a server answers again, click Retry on the deployment that failed.