Troubleshooting

Build failures

My build fails with “no such file or directory”

Your Dockerfile references a file that doesn’t exist in the repo at build time. Make sure the file is committed and the path in COPY or ADD is correct relative to the repo root.

My build fails with “exit code 1” and no clear error

Look at the full build log — the actual error is usually a few lines above the final failure. Common causes:

A RUN command that fails silently (e.g. npm test running in the build stage)
Missing system packages — add them with RUN apt-get install -y ... (Debian) or RUN apk add ... (Alpine)
Network errors during package install — click Redeploy to retry

My build succeeds but the container exits immediately

Your app is crashing at startup. Check the Logs panel on the project card (not Build Logs) to see what your app printed before it exited.

Common causes:

A required environment variable isn’t set — add it in the Environment panel and redeploy
Your app binds to localhost instead of 0.0.0.0 — change the bind address so traffic from outside the container can reach it
Your app listens on a different port than what’s configured — delete and recreate the project with the correct port

Deployment

My project is stuck in “creating”

A build is running. Builds typically take 1–3 minutes for small apps. Click Build Logs to watch progress and check for errors.

If it’s been more than 10 minutes with no activity in the build log, the build may have silently hung. Click Redeploy to retry.

My project shows “failed”

The last build or startup attempt failed. Check Build Logs for build errors and Logs for runtime errors.

Pushes aren’t triggering automatic redeploys

Check the webhook is active in GitHub under Settings → Webhooks. Look for a green tick next to recent deliveries.
If deliveries show a red ×, click the entry to see the response. A 401 means the signature check failed — delete and recreate the project to reset the webhook secret.
Make sure you’re pushing to the branch configured for the project (default: main).

HTTPS and certificates

My custom domain shows a certificate warning

Wait up to 5 minutes after DNS propagates — certificate issuance takes a moment. If it doesn’t resolve:

Run dig CNAME your-domain.com and verify the CNAME points at your *.weekendbuilder.io subdomain
Check there are no conflicting A records or CAA records blocking Let’s Encrypt
Remove and re-add the custom domain to retry certificate issuance

My `*.weekendbuilder.io` URL shows a certificate warning

Try a hard refresh. If the warning persists, contact support.

Account

I signed in but see “not on the invite list”

WeekendBuilder is invite-only during the beta. Join the waitlist to request access. If you believe you should have access, make sure you’re signing in with the correct GitHub account.

Click Sign out in the top right of the dashboard, then click Sign in with GitHub again. If your browser has a GitHub session for the wrong account, use the “Sign out of GitHub first” link on the login screen before signing in.