Troubleshooting

If your deploy is stuck or fails:

1. Check the deploy console for error messages.

2. Ensure your project builds locally: cd your-project && npm install && npm run build.

3. If your app requires environment variables, add them during the upload flow.

4. Contact support with your TRK-ID (shown in the error screen).

Sites on the free plan go to sleep after 30 minutes of inactivity. They wake up on the first visitor request (1-2 seconds). You'll see a 'Mission Warming Up' indicator.

1. Verify DNS is configured correctly (A or CNAME record).

2. DNS propagation can take up to 48 hours.

3. Use the 'Verify' button on the Domains page to check DNS status.

4. Ensure your domain isn't already pointing to another service.

After changing env vars, redeploy your mission for the changes to take effect. Dynamic sites (Node.js, Next.js) require a restart — redeploying triggers this automatically.