Limits and troubleshooting
Limits
Section titled “Limits”| Limit | Value |
|---|---|
| Build time | 20 minutes per build |
| Build with no output | Stopped after 10 minutes of silence (“build stalled”) |
| Deploys | 30 per hour per account; one at a time per app |
| Memory per app | 512 MB |
| CPU per app | 0.5 vCPU |
| Custom domains | 5 per app |
| Folder uploads | 50 MB compressed, 500 MB unpacked |
| Environment variables | 200 per app, 64 KB total |
Your plan also sets how many apps you can have and how many build minutes are included each month. See Plans. Apps don’t sleep: they keep running until you delete them.
“Nothing is live here”
Section titled ““Nothing is live here””404 · Not found — Nothing is live here. <hostname> isn’t connected to anything on DockHive.
You see this page when an address isn’t connected to anything on DockHive. Common reasons:
- the app (or tunnel, or workspace) was deleted or renamed,
- the address was never deployed, or there’s a typo,
- a custom domain points at DockHive but isn’t verified yet, or was added to a different app.
If it’s your app, open the console and check the app’s address and its Domains & TLS tab.
“This app is unreachable right now”
Section titled ““This app is unreachable right now””Unreachable — <hostname> is on DockHive, but it isn’t responding.
The address belongs to an app, but the app didn’t answer. It may be offline, restarting, or crashing on start. For a tunnel, the computer behind it may be asleep or disconnected. This is usually temporary.
If it’s your app:
- Check the Logs tab for errors when the app starts.
- Check the latest deployment’s status and log.
- Redeploy, or roll back to the last version that worked.
Error pages your own app returns (such as its own 404) are shown as-is.
Common deploy errors
Section titled “Common deploy errors”Health check failed: no HTTP response
Section titled “Health check failed: no HTTP response”The app started but didn’t answer in time.
- Make it listen on
0.0.0.0(not127.0.0.1orlocalhost) and on the port in thePORTenvironment variable. - With a framework preset, set the Port in Builds & Settings if your app uses a fixed port.
- Read the app output shown under the error for the real cause (a missing variable, a crash on start).
The app refuses its public address
Section titled “The app refuses its public address”Some frameworks only answer to hostnames you allow:
- Django: add your
.dockhive.appaddress and custom domains toALLOWED_HOSTS. - Rails: add them to
config.hosts. - Vite dev or preview server: serve the production build instead.
- Invalid Host header: configure your server to accept your public hostname.
Access to the repository was denied
Section titled “Access to the repository was denied”The repository is private and DockHive can’t read it. In the new-app wizard, use Grant repository access (or reconnect GitHub), or add a Repository Access Token in Builds & Settings.
Your app needs environment variables
Section titled “Your app needs environment variables”Add the listed variables and redeploy. See Environment variables.
Root directory does not exist
Section titled “Root directory does not exist”Set Root Directory to the folder that contains your app, relative to the repository root.
Build minutes used up
Section titled “Build minutes used up”On the Free Tier, builds stop when the month’s included build minutes are used. Running apps aren’t affected. Upgrade, or wait for the next billing period.
Interrupted by a restart
Section titled “Interrupted by a restart”Rarely, a deploy is interrupted by platform maintenance. Click Redeploy.
Still stuck?
Section titled “Still stuck?”Email partners@dockhive.io with your app’s name and what you tried.