OneBitDeploy
Reference

Troubleshooting

Common issues when deploying on OneBit Deploy and how to resolve them.

A quick reference for the most common issues.

My build failed

  • Open the Logs tab, choose Build and read the build output — the error is usually near the end. (Build log on the update in the Deployments tab opens it too.)
  • Confirm the app builds locally with the same install/build commands.
  • Make sure any required environment variables are set, including build-time variables like NEXT_PUBLIC_*.

My app deploys but returns errors

  • Check the runtime logs in the Logs tab (Runtime; Errors only shows just the errors) for stack traces.
  • Verify your start command and that the app listens on the expected port.
  • Confirm your database connection string is set correctly as an environment variable.

My custom domain isn't working

  • Make sure you created the exact DNS record shown on the app's Domains tab.
  • DNS changes can take time to propagate — wait for the record's TTL and retry.
  • See Custom domains & SSL.

The first request is slow

Apps on the Free plan sleep when idle, so the first request after a quiet period wakes the app and is slower. Starter (₦10,000/month) and above keep apps always on.

My database won't connect

  • Confirm the connection string is correct and stored on the app's Environment tab; Test connection on the database's page checks the database itself.
  • Saving a key restarts the app so it picks the value up; give it a minute before you test again.
  • See Connecting to a database.

Still stuck? Open Help in the console (or press Ask us), choose My app and the app, and say what you expected and what happened instead. OneBit can already see your apps and bills, so you do not need to paste IDs or logs.

On this page