Troubleshooting
When something breaks, the answer is almost always already on screen. Every deploy streams its full build output live in the dashboard: open the project, open the deployment, and read the build logs. The stream includes the git clone, the dependency install (for example the npm install output), the framework build (for example next build), the image push, and the rollout. If a deploy ends in FAILED instead of RUNNING, the exact error is almost always visible in those logs — read them before anything else.
A deploy moves through a simple lifecycle: it is created, it builds, and it finishes as RUNNING (succeeded) or FAILED. The pages below cover the failure modes for each stage and for the systems around them.
Find your error
Section titled “Find your error”Match the literal error string or symptom you are seeing to the right page:
| You see | Go to |
|---|---|
Access denied connecting to a MySQL database | Database connection issues |
| ”Add a payment method to continue” | Account, billing & limits |
| ”No index.html at the root” | Build & deploy failures |
| A 402 bandwidth-block page served on your site | Account, billing & limits |
| Build succeeds but the container never becomes healthy | Build & deploy failures |
Troubleshooting guides
Section titled “Troubleshooting guides”Everything between “push” and RUNNING: build errors, dependency installs, start command, port binding, out-of-memory, repo access, upload limits, slow builds, and cold starts. Example symptoms: the build log ends in a compile error, the deploy stays FAILED, or the container never becomes healthy after a green build.
Your app can’t reach or authenticate against a PandaStack database: MySQL username encoding, passwords, TLS, suspended free databases, and connection limits. Example symptoms: Access denied errors on MySQL, or a free database that stopped responding.
Anything the platform blocks before or around your workload: the payment-method gate, email verification, bandwidth limits, plan limits, and Pro-only features. Example symptoms: “Add a payment method to continue”, or visitors hitting a 402 bandwidth-block page on your site.
Still stuck?
Section titled “Still stuck?”Copy the relevant lines from your deployment’s build logs and email support@pandastack.io — the logs are the fastest way for us to see what happened.