Fix common deploy problems

Find your symptom below. If it isn't listed, check the build log in Deployments and the Logs tab, then contact support with the app name.

"Add deploy key" or access can't be verified

Cause: Kubana can't read the repository.

Fix:

1. In GitHub, open the repository → Settings → Deploy keys and check that the key from the app's Overview tab is there, pasted in full.
2. Make sure you added it to the same repository you entered in Kubana.
3. Choose I've added the key, verify access again.

The Deploy button is disabled

Cause: setup isn't finished. Fix: check that:

• the deploy key is verified,
• a branch is selected (Configuration),
• the build directory is set (frontend apps),
• the Laravel and PHP versions are set (Laravel apps).

"Not enough credit" / insufficient balance

Cause: a paid app needs at least 72 hours of its price in credit for its first deploy, or to redeploy after terminating.

Fix: top up your credit, or choose the free size for a small frontend app.

"You're using all 2 free apps"

Cause: your account already has 2 free apps that aren't terminated, across all projects.

Fix: terminate a free app you no longer need, or pick a paid size. See Stop, terminate or delete an app.

The frontend deploys but shows a blank page or 404

Cause: usually the build directory doesn't match where your build writes its files.

Fix: set it to your framework's output folder, for example /dist (Vite, Vue), /build (Create React App) or /out (Next.js static export). Saving it doesn't redeploy, so deploy again afterwards.

A Laravel deploy fails

Check the Laravel requirements. The usual causes:

• artisan isn't at the root of the repository,
• composer.json requires a different Laravel major version than the one you selected,
• on Laravel 11 and later, the /up health route is missing.

A new environment variable has no effect

Cause: variables apply on the next deploy. Fix: redeploy. On Laravel, VITE_* variables aren't available during the asset build. See Set environment variables.

A pushed commit didn't deploy

• Check that auto-deploy is on and the push was to the selected branch.
• If a deployment was already running, the push was ignored. Deploy again manually.
• In GitHub, open the webhook's Recent Deliveries to see whether it was delivered. See Deploy automatically on every push.

A custom domain fails verification

Cause: the domain's DNS doesn't point only at Kubana.

Fix: set the A record to 62.238.7.246 and remove any other A/AAAA records on that name. Wait for DNS to update, then try again. See Use your own domain.

The domain is attached but HTTPS doesn't work yet

The certificate is still being issued. Give it a few minutes.