XiotBox Documentation
Odoo 19 · XiotBox 19.0.2
Troubleshoot without guessing
Start at the failed boundary and change one thing at a time.
Fast diagnosis
| Symptom | Check first | Likely boundary |
|---|---|---|
| Runtime health URL fails | DNS, certificate, service status, port 443 | Internet → Runtime |
| 401/403 in Runtime logs | Runtime/SocketD tokens and database name | Runtime → Odoo |
| Client login fails | Runtime URL and account state | Desktop → Runtime |
| Computer never appears | SocketD reachability and client logs | Desktop → SocketD |
| Printer appears offline | OS printer, client process, heartbeat | Desktop device |
| Job stays new | SocketD connection and target computer | Odoo → SocketD |
| Job sent but no paper | Desktop spooler and selected printer | Client → printer |
Collect evidence
- Write down the exact UTC/local time and affected Odoo job ID.
- Capture Odoo logs around that time.
- Capture Runtime and SocketD logs, with tokens redacted.
- Record all component versions and operating systems.
- Test DNS and HTTPS from the affected desktop network—not only from the server.
- State whether one user/printer or every user/printer is affected.
Safe reset order
Restart the desktop client, then Runtime/SocketD, and only then Odoo if necessary. Recheck the existing job before submitting another. Do not regenerate tokens during diagnosis unless logs specifically prove credential exposure or mismatch.
Still blocked? Send the evidence above to support@xiotbox.com. Never email passwords, API keys, full database backups or unredacted customer documents.