Troubleshooting Deployment Failures

Troubleshooting Deployments

Deployment failures can occur at any stage of the pipeline. This guide covers the most common issues and how to resolve them.

Common Build Failures

• Dockerfile not found — Ensure your template has a valid Dockerfile in the expected location.
• Dependency installation failed — Check that your package.json or requirements.txt lists all dependencies correctly.
• Build timeout — Large builds may exceed the time limit. Optimize your Dockerfile with multi-stage builds and caching.

Container Startup Failures

• CrashLoopBackOff — The container starts and immediately crashes. Check the application logs for error messages.
• OOMKilled — The container exceeded its memory limit. Consider upgrading your plan or optimizing memory usage.
• Port binding error — Ensure your application listens on the expected port (usually 3000 or 8080).
• Missing environment variables — Verify all required environment variables are set in the application configuration.

DNS and SSL Issues

• DNS not resolving — DNS propagation can take up to 5 minutes. Wait and try again.
• SSL certificate pending — Certificate issuance requires DNS to be fully propagated first. Allow up to 10 minutes.
• Mixed content warnings — Ensure your application uses relative URLs or HTTPS for all resources.

Checking Logs

1. Open your application from the Apps page.
2. Navigate to the Deployment tab.
3. Click View Logs to see build and runtime output.
4. Use the filter controls to narrow down by log level or time range.

Getting Help

If you can't resolve the issue:

• Submit a support ticket from the Help section.
• Include the application ID, deployment timestamp, and relevant error messages.
• Our team will investigate and respond within 24 hours.