Troubleshooting deployments

Check the install and build commands in your project configuration, and that the root directory points at the folder containing your package.json (or equivalent). The build log shows the exact command that failed.

On Pro and Team, click Explain with AI on the failed deployment for a plain-language diagnosis.

Almost always a port or host binding issue: your server must listen on the port configured for the project (injected as the PORT environment variable for Node presets) and bind to 0.0.0.0, not localhost or 127.0.0.1.

Your GitHub token may have expired or been revoked. Sign out and sign back in with GitHub — this refreshes the stored token, and repositories will load again.

Confirm the CNAME record points at your project subdomain and give DNS time to propagate (minutes to 48 hours). You can check propagation with an online DNS lookup tool; the certificate is issued automatically once the record resolves.

If pushes no longer deploy, reconnect the webhook in Project → Settings → Git, and check that auto-deploy is enabled for the project.

Email hello@darmicloud.tech with your project name and the deployment's error message — we read everything.