Fix common CloudPloy problems
Start with the app page in the console. It shows the steps of each deploy, the build log, and the latest lines your app writes. Most problems show up there.
A deploy failed
- Open the deploy on the app page and find the first step that failed. The build log shows the error from Composer, npm, Nixpacks or Docker.
- The old version keeps serving while you fix it. Use Rollback if the version that is live is the broken one.
- "The repository has no Dockerfile": CloudPloy found a Dockerfile when the app was created, but the branch has none at its root now. Add it back, or create the app again so CloudPloy detects the stack anew.
- "WordPress apps are not supported by this deploy engine yet" or "Apps with a database are not supported by this deploy engine yet": CloudPloy cannot deploy these today.
The deploy never becomes ready
CloudPloy sends traffic to a new container only after the app answers on its port. Make sure the app listens on the port in the PORT environment variable, on 0.0.0.0, not only on localhost. Check the app logs for a crash at start, often a missing environment variable.
A plan limit stops a new app or server
Each plan allows a number of servers and apps, and a largest server size. CloudPloy refuses a new app, a new server or a larger size above the limit. Nothing that runs is stopped. See Pricing to compare the plans.
A server shows as unreachable
- Servers in your AWS account: check in the AWS console that the instance is running and that the CloudPloy access key is still active.
- A server you connected over SSH: check that it is on, that SSH is open on the port you entered, and that the CloudPloy key is still in
~/.ssh/authorized_keys.
AWS refuses a launch
CloudPloy checks the instance role before each launch. If the role or the policy is missing or out of date, the console shows the steps to fix it. Follow the AWS guide and paste the latest policy.
A domain does not verify
DNS changes can take a while to reach everyone. Check that the record at your DNS provider matches the one the console shows, then choose Verify again. See Add a custom domain.
Still stuck?
Email hello@cloudploy.com with your team name, the app, and what you see.