Developer Guide For Known Issues

This guide contains known issues, their solutions, and developer recommendations.

Reached Heap Limit Allocation Failed Error

This error occurs when the server does not have sufficient RAM. To build frameworks like Next.js, Nuxt.js, or React Router, you need at least 2GB of RAM depending on your application size. If you perform multiple deployments simultaneously on a low-RAM server, you may encounter this error as the server may be insufficient for handling 2 deployment processes at the same time. You can use build queue limits to prevent this issue.

Visit the server deployment queue section for more information. https://app.depfloy.com/servers/{serverId}/queue

Uncommitted Commits During Deployment

This error may occur when files under source control within the site directory have been changed by the application and will be overwritten by the fresh deployment. Depfloy will always reset your project to the main branch. Remember that if your application makes changes to files, they will be reset after each deployment.

Project Stuck in Deploying Status

Rarely, your application may get stuck in the “deploying” status. In this case, you can reset the deployment status by hovering over the relevant project in the project management panel and clicking the three-dot button on the right side, then selecting the “reset deployment status” option.

502 Error After Deploying a Node.js Project

If your Node.js project returns 502 errors after every other deployment, it is likely caused by a hardcoded port in a custom nginx configuration. Depfloy uses blue/green deployment for Node.js projects, which rotates the application port on each deployment. If your nginx configuration uses proxy_pass http://127.0.0.1:3093 instead of the upstream alias, it will point to the old port after deployment.

Solution: Replace the hardcoded port with the upstream alias in your nginx configuration. See Nginx Configuration — Node.js Upstream for details.