Troubleshooting

Build fails

Read the first failing step, not the last line. Missing lockfiles, unsupported runtime versions, and files excluded by .dockerignore are the usual causes. Build the image locally to see the full output.

docker build -t myapp .
docker run --rm -p 3000:3000 myapp

Container exits with 137

Exit 137 usually means the container ran out of memory. The demo tier has 128 MB, which is below many application servers. Reduce memory use or move to a paid app with a larger limit.

Health check never passes

• • Confirm the app listens on 0.0.0.0.
• • Confirm the project port matches the app.
• • Check runtime logs for a crash or a missing environment variable.
• • Make sure startup finishes inside the health-check window.

502 or 404 from the web

A 502 usually means the app is not answering on its internal port. A 404 usually means the hostname is not attached to a running app, or DNS still points elsewhere.

Certificate warning

Wait for DNS propagation, then reload. A new custom domain can take a few minutes before its certificate is ready. Confirm the record is a CNAME to apps.goldenhour265.com.

Database connection refused

• • Attach the database to the app before deploying it.
• • Redeploy after attaching so the variables reach the container.
• • Use the internal hostname, not localhost.
• • Check the credentials in the database's Credentials dialog.

Demo app is asleep

Demo apps stop after 15 minutes without traffic. Open the project and press Start to wake it. For a live service, move to a paid app.

Still stuck?

Send us the project name, the commit, and the first failing line from the build log. Never send passwords, API keys, or private keys.