Skip to main content

Troubleshooting

Troubleshooting pages should start from the exact failing stage and then point to the narrowest safe command.

First Rule​

Do not retry a spend command until you know whether the previous attempt created an Acurast deployment, funded a Hub session, registered a job, or activated a route.

Start read-only:

proof baran preflight --quote --json
proof baran deploy status
proof baran deploy doctor --report <report.json>
proof baran status --json

Pages​

  • Deployment Failures: preflight, upload, funding, Acurast, registration, timeout, and resume diagnosis.
  • DNS And ACME Failures: canonical DNS, customer CNAME, challenge delegation, certificate authorization, and SNI probes.

Redaction​

Do not paste decrypted logs, full private workflow snapshots, local secret files, private keys, seeds, bearer tokens, DNS tokens, or raw runtime env into public issues.