Troubleshooting

When something goes wrong, the logs almost always tell you why. Here's where to look and where to go next.

Build and run logs

Every deployment keeps a full build log. Open Project → Environment → Deployments → deployment to read it — logs stream live while the build runs and stay available after it finishes. If a deployment failed, the error message is shown above the log, and the log usually contains the exact line that caused it. See Build logs for filtering and copying.

AI-suggested fixes

When a build fails, Velumi's built-in AI reads the error and suggests a fix right in the dashboard — pointing at the likely cause and what to change. It's the fastest way to get unstuck without digging through the full log yourself.

Common issues

• A deployment failed — check the error above the build log, then the AI suggestion. Statuses are explained in Deployment lifecycle.
• The site is down or returning errors — check the environment status. A failed build doesn't take down a running environment, but a stopped environment serves no traffic.
• A domain or DNS isn't working — see Troubleshooting DNS.
• GitHub repo missing or build can't access it — see Troubleshooting GitHub.
• A payment failed or projects are suspended — see Failed payments.

Still stuck?

If the logs and AI suggestion don't resolve it, contact support with your project name and the deployment ID — it helps us find the issue fast.