Troubleshooting

Build failures

“no registry credentials configured”

You haven’t connected a container registry. Go to Registry Credentials in the sidebar and connect your GHCR account.

“repository not found”

The GitHub App doesn’t have access to the repository. Make sure you selected the repository when installing the GitHub App. You can update the installation at github.com/settings/installations.

“failed to clone”

The GitHub App installation may have expired or been revoked. Try reconnecting the repository from your app’s detail page.

Build exits with non-zero code

Check the build logs for the specific error. Common causes:

Missing dependencies in your Dockerfile
Build command fails (e.g. TypeScript compilation errors)
Tests failing during build

Deployment failures

“pool exceeded”

Your organization has reached the CPU or memory limit of your plan. Either reduce resource allocation on existing environments or upgrade your plan.

App returns 502 Bad Gateway

Traefik can reach your pod but your app isn’t responding on the configured port. Check:

Your app is listening on the correct port (configured in resource settings)
Your app started successfully (check deployment logs)
Your /health endpoint returns 200

TLS certificate pending

After first deployment, the TLS certificate can take a few minutes to provision. If it stays pending for more than 10 minutes, check that:

Your domain’s DNS is pointing to Podway
Port 80 is reachable from the internet (for HTTP-01 challenge)

Auto deploy not triggering

Check that auto deploy is enabled for the environment
Verify the branch filter matches your pushed branch
Ensure the GitHub App webhook is configured — check your repository’s Settings → Webhooks

App not accessible after deployment

Check that the deployment status is Active in the dashboard
Verify the default domain resolves: dig {app-slug}-{env-name}.podway.dev
Wait a few minutes for DNS propagation after first deployment