Troubleshooting

The app returns 502 or does not load

A 502 commonly means the proxy cannot reach a healthy application process.

1. Check Settings → Logs for startup errors or crashes.
2. Confirm that the configured exposed port matches the port your process uses.
3. Check that the app listens on an accessible interface, usually 0.0.0.0 in a container.
4. Confirm that required environment variables and services are configured.
5. Ask the agent to inspect the exact error, make a targeted fix, and verify a new deployment.

Redeploy after correcting the cause. Repeating the same deployment without new evidence may reproduce the failure.

A build fails

Inspect the build logs and the first meaningful error. Common causes include missing dependencies, an incorrect build command, unsupported runtime versions, or a Dockerfile that does not match the project.

Ask the agent to fix the specific failure and rerun the relevant build or check. A failed check should not be presented as successful just because another command completed.

The task stalls, repeats itself, or pauses

Open the task’s plan, checks, and activity. Read the pause reason and identify whether the blocker is usage, a work budget, missing permissions, or a failed operation.

Stop a repeating task, explain the desired next step, and continue from the saved work. If it cannot perform the action with its available tools, the agent should tell you what remains to be done. See tasks and verification.

A connection error appears

Check whether the problem affects the chat connection, GitHub, a build, or the deployed app. Record the exact error and the action that triggered it. Reopen the project to recover saved task state, and inspect activity before resending work that might already be running.

If GitHub access is failing, confirm the installation and repository permissions. Preserve unsynced changes and commits; do not recreate the workspace as a first troubleshooting step.

Daily allowance is depleted

Your allowance resets at midnight UTC. Use an available daily reset or a plan with more usage if you need to continue sooner. Increasing the work budget alone does not restore allowance.

Contact support

Open Help inside AppJet. Include your GitHub username, repository, branch, exact error, approximate time, and what you expected to happen. Share the relevant logs without passwords, API keys, or other secrets.