Troubleshooting

Fixes for common problems, and how to send us diagnostics.

A bot says it can’t reach its AI

Check Settings → Engines. Make sure Praxiom is connected (or that the provider the bot uses is set up), and that the key is still valid. For local models, make sure the model server is running.

Bots stopped taking new work

The organisation may have hit its monthly budget. Check Organisations → Usage This Month… and raise the limit in Brand, Budget and Billing….

“Permission denied” on another organisation’s files

Only one organisation is open at a time, and the others are locked on disk. Switch to that organisation first.

macOS or Windows blocks the installer

macOS: right-click the app and choose Open. Windows SmartScreen: More info → Run anyway.

The phone won’t pair

Pairing codes expire after five minutes; create a new one. For Direct Wi-Fi pairing both devices must be on the same network. Try Secure HTTPS pairing if the network blocks local connections.

Webhooks don’t fire

OrraBot must be open, the webhook turned on, and the URL current. If you generated a new private URL, update the sender.

Send us diagnostics

Choose Settings → General → Diagnostics → Export Diagnostics…. It saves a text file with versions, settings and recent logs, with secrets removed. Attach what it tells you to a bug report.

Where your data lives

Bots, chats, schedules and memory are stored per organisation under ~/.orrabot/orgs/. Make a backup before moving or resetting anything.

Still stuck? Contact us