FAQ

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. Paths in Dockerfile are relative to the build context (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 — trigger a manual redeploy to retry

My build succeeds but the container exits immediately

Your app is crashing at startup. This is a runtime error, not a build error. Check the Logs panel (not Build Logs) on the project card 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 — update the Port setting (delete and recreate the project)

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:

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

My *.weekendbuilder.io URL shows a certificate warning

This shouldn’t happen — the wildcard cert is managed by WeekendBuilder. Try a hard refresh. If the warning persists, contact support.

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.

How do I change the port after creating a project?

Port configuration is set at project creation and can’t be changed afterwards. Delete the project and recreate it with the correct port.

Can I deploy multiple branches of the same repo?

Yes — create separate projects, each pointing at a different branch. They’ll get separate subdomains and URLs.

Limits

How many projects can I have?

Each account can have up to 5 active projects. Delete a project to free up a slot.

Is there a build timeout?

Builds time out after 10 minutes. If your build regularly takes longer than that, look at the Build caching section in Deploying from GitHub to speed things up.

What resources does each container get?

Containers share the host’s resources. There are no hard limits set per-container during the invite beta. This will change before public launch.