Support
How to get help with AI Workbench, nodes, the mobile app, Mojo Up AI Cloud and self-hosted AIOE, and what to send.
Help yourself first
- Search these docs. Press Ctrl K (or ⌘ K on a Mac), or use the search box.
- Troubleshooting covers the problems people meet most: Troubleshooting.
- Release notes say what changed in each version, and whether updating fixes what you see: Release notes.
Contact Mojo Up
| For | |
|---|---|
| Questions, problems, plans and pricing | contactus@mojoup.com.au |
| A security problem | security@mojoup.com.au. See Report a vulnerability. |
| Your personal information, or deleting your account when you cannot sign in | privacy@mojoup.com.au |
If your organisation runs its own AIOE, start with your own IT team: they run the platform and can see its logs.
What to send
The more of this you include, the faster we can help.
- What you were doing, what you expected, and what happened instead. The exact words of any message help most.
- Where: Mojo Up AI Cloud or your organisation's own AIOE; and for the workbench, your operating system.
- Versions: the AI Workbench version; for a node, the output of
mojoup-node version; for AIOE, theversionthathttps://<your AIOE>/healthzreturns. - For a node: the output of
mojoup-node doctorandmojoup-node status, and the end of its log (mojoup-node logs -n 200). - When it happened, with your time zone.
Never send passwords, tokens, API keys or the contents of .env files. If a log might contain a secret, remove it first.