Troubleshooting
This page is the index. Pick the recipe that matches the symptom you are seeing — each recipe lists the expected error code(s), likely causes, a verification command, and the concrete fix steps.
Find your recipe by symptom
| Symptom | Recipe |
|---|---|
| Printer won't pair (Bluetooth / USB / Serial / TCP) | Device pairing failures by transport |
| Command timed out or seems stuck | Command timeouts and the 180s sweep |
| Webhook stopped firing or got auto-disabled | Webhook delivery failures |
| ANAF rejected an MF / JE / P7B report | ANAF report rejection |
X-EBon-Signature verification fails on your endpoint | HMAC signature mismatch |
API returns TIER_LIMIT_EXCEEDED | Tier limit exceeded |
error.code (HTTP) or errorCode (FiscalError on commands), not on the human-readable message — codes are stable across releases. The full catalogue lives in Errors reference.Get more help
If none of the recipes resolve the issue, open a support case at support@e-bon.ro or e-bon.ro/contact. Include the device ID, the affected command ID or delivery ID, and the relevant error code — those three identifiers let support trace a request end-to-end.
How e-bon is organized
The three pieces of the e-bon platform — the Cloud Portal, the E-BON App for Android and the public REST API — and how a fiscal receipt flows between them.
Fix device pairing failures by transport
Recognise the symptom when a fiscal printer fails to pair over Bluetooth, USB, Serial or TCP, then apply the right fix per transport.