Help

Troubleshooting

Last updated August 2026

Solutions to common issues you might encounter when using Spawned.

Deployment Issues

Check your Dockerfile - If your project includes a Dockerfile, make sure it builds successfully locally with docker build . before deploying.
Missing dependencies - Ensure your package.json, requirements.txt, or equivalent dependency file is committed to the repository. Spawned builds from your source code and needs all dependencies listed.
Context field - Use the Context field when creating a deployment to provide additional instructions. If your app requires specific build arguments, environment variables, or build steps, describe them there.

Provisioning cloud infrastructure typically takes around 1-10 minutes. Please be patient while we wrangle with the underlying cloud providers.
Expand logs in your project’s version history tab and identify where things are stuck.

Check logs - Select your container from the infrastructure canvas, and click the logs tab. Container stdout is streamed directly from your cloud provider.
Port configuration - Make sure your application listens on the correct port.
Environment variables - If your app requires API keys or configuration, add them as secrets through a ‘Secret’ component, and connect it with your container.
Memory limits - If your container is being killed (OOMKilled), your application may need more memory than the default allocation.

Spawned needs your domain delegated to the nameservers shown in Settings → Domains. Confirm you have set those nameservers, or added the matching NS records for a subdomain, at your registrar.
If your registrar offers a proxy option, turn it off so the records resolve directly.
Delegation usually propagates within 5-30 minutes but can take up to 24 hours. Verify with dig NS example.com or dnschecker.org.

Your delegation is confirmed and a TLS certificate is being issued automatically. This usually finishes within a few minutes.
If it does not complete, check that any CAA record on your domain allows Amazon to issue certificates.

Confirm the nameservers at your registrar match exactly what Spawned shows, with no leftover conflicting records.
Delete the domain and add it again to trigger a fresh attempt.

See Custom Domains for the full setup flow.

Make sure you’ve installed the Spawned GitHub App in Settings.
Check that the repository is included in the app’s access. Go to GitHub > Settings > Applications > Spawned and verify the repository is selected.
For organization repositories, the app must be installed on the organization, not just your personal account. This requires organization admin permissions.

Spawned builds from the ref set on the component’s source — a branch, tag, or commit SHA, defaulting to the repository’s default branch. Make sure your changes are on that ref; a pinned tag or SHA never picks up new commits.
CI/CD only applies to GitHub repository sources. Docker image and file upload sources won’t be updated.
Trigger a redeployment manually from the Deployments tab.

Verify the IAM Role ARN you entered matches exactly what was created in your AWS account.
Check that the IAM role has the correct trust policy allowing Spawned to assume it.
Make sure the role has the required permissions as described in the setup wizard.

All resources are deployed to eu-central-1 (Frankfurt). Make sure you’re looking at the correct region in the AWS console.
Resources are tagged with your Spawned project name. Use AWS Resource Groups or tag filters to find them.

If you’re still stuck: