Common problems & fixes

Something not working? Most hiccups have a simple explanation, and The Deployer often starts fixing them for you automatically. This page covers the problems people hit most, what each one means, and exactly what to do next.

"My deployment failed"

What it means: a step in the build or launch didn't complete. This is common and usually recoverable.

What to do:

1. Don't panic — when a deploy fails, a Recovery Agent typically kicks in and tries to fix the cause and continue on its own. Give it a moment.
2. Open the deployment's logs to see what happened and whether recovery is still working. You'll find them from the project's Activity list — see launching & reading the logs.
3. If it's genuinely stuck, you can retry the deployment. If the logs point at a specific cause (like a missing setting), fix that first, then retry.

"My URL is unreachable" (the Unreachable badge)

What it means: The Deployer checks that your app really responds before it calls a deploy a success — it's deliberately cautious ("fail-closed"), so it would rather tell you the truth than show a green light on a broken app.

What to do:

1. Wait a little — the Recovery Agent may still be getting the app healthy.
2. Check the deployment logs for what's happening (reading the logs).
3. If you just connected a custom domain, remember that DNS can take time to propagate (see the next section and connecting a custom domain).

"I'm getting credential errors"

What it means: a cloud or GitHub key has expired, been revoked, or was entered incorrectly, so The Deployer can no longer sign in to your account.

What to do:

1. Go to the Connections page and replace the credential. The Deployer checks the new key works before saving it, and keeps the same connection so your projects keep running. Replacing a credential requires your account password.
2. If a deployment failed because of this, you'll often see a card offering a one-click replace right there — use it, then click Redeploy.

"DNS isn't propagating" / my domain doesn't work yet

What it means: DNS is the internet's address book, and changes to it (like pointing your domain's nameservers at your cloud) aren't instant — they spread across the internet gradually.

What to do:

1. Give it time — this can take minutes to a few hours. It's normal.
2. Double-check you set the nameservers or records exactly as shown. See connecting a custom domain.
3. The Deployer keeps checking and verifies automatically once your domain is live, so you don't have to babysit it.

Still stuck?

Ask the AI assistant a plain-language question, or see getting more help.