BryanNetError codes and support information checklist
Prerequisites and authority
Use this reference with your installed release. Internal implementation routes and settings are not public integration contracts.
Interpret errors by their layer
| Observation | Likely investigation |
|---|---|
| DNS lookup fails | Name/endpoint configuration |
| TCP connection refused | Service listening or selected port |
| TCP timeout | Routing/firewall/path or stopped host |
| Authentication rejected | Identity, credentials or session validity |
| Permission/feature rejected | Role, module, entitlement or license |
| HTTP 500 | Backend/dependency exception |
| Operation completed with failures | Target-level processing errors |
| Backup WARNING | Destination/pruning details, not full protection |
These are diagnostic categories, not a promise of a particular machine-readable error code. The final error catalogue must list the actual release code/message, meaning, retryability, affected workflow and authoritative troubleshooting link.
Do not retry an economic or destructive action solely because the client timed out. The server may already have completed it. Inspect its record/reference before repeating.
Collect version, OS, time/timezone, affected surface, record/operation IDs, scope, exact redacted error, recent changes and checks already performed. Keep passwords, tokens, encryption/recovery keys and unrelated customer data out of reports.
Use the incident template and diagnostic checklist. Escalate after preserving evidence when the next step could replace data or the system's economic/access state is uncertain.
Related guides
Related guides: Configuration reference (env vars, ports, URLs), Docker services, Compose files and persistent volumes, Database diagnostics and safe query reference, Subscription and provisioning state model.