Tell us what is broken or missing

Send a report

• In the window: Report a problem at the bottom of the left column, or Settings → Reports. Choose A problem or An idea, write a few words, and press Show what will be sent. Nothing leaves the machine until you press Send on the next step.
• On a server: moxivue feedback "what happened". Add --idea for a suggestion, --diagnostics to include diagnostics and --email you@example.com if you want a reply. It prints the report and asks before sending.

Reports work without signing in and without an account, because the problem may be exactly that.

Ideas and votes, in public

To suggest a feature where others can see and vote on it, or to ask a question, use MoxiVue community on GitHub. A bug can also be reported there in public, with a short form; the report from the app is still the better way when the problem needs details of your machines. You need a GitHub account to post or vote. Everything there is public, including your GitHub user name, and GitHub's own terms and privacy statement apply to it. Never post a security problem there (see Report a security problem), nor anything about your own machines that you would not want public: send that from the app as above.

What a report contains

Always: the kind of report, your text, the MoxiVue version, which package is installed (desktop or server) and the system (for example "Ubuntu 24.04, kernel 6.8, x86_64").

Only if you give it: an email address for a reply.

Only if you tick Add diagnostics:

• the result of MoxiVue's self-check (moxivue verify);
• how many faults of which kind are open (not their text);
• the last 200 lines the agent logged and the last 50 of the helper.

Before you see the diagnostics, the names in them are replaced by placeholders such as <host>, <user> and <ip-1>: host and user names, home folders, email addresses, IP and MAC addresses, device and account ids, keys, the names of your account, sites and networks where they are recognised (names of three or more characters), and the hosts of web addresses other than ours. The preview shows the text after that step, and that text is what is sent.

The diagnostics hold no readings and no history. They do include the last lines of MoxiVue's own log, which are free text, so read the preview. Your own text is sent as you wrote it, so leave out anything you do not want us to read.

Where it goes

The report is encrypted on your machine to a key whose private half is kept off our servers. It is then sent to dispatcher.moxivue.com, which stores what it cannot read, with the time and the kind of report. We fetch the stored reports and open them on a computer that holds the key. Stored reports are deleted from the server after 90 days; the server's encrypted backups, and the encrypted copy of those backups on one computer of ours, hold them for up to 35 days longer, and the copies we have fetched stay on the computer that opens them until we delete them.

The server limits reports to six an hour from one address and 256 KB each.

Crash reports

Crash reports are off. When a part of MoxiVue stops on an internal error, it keeps a small note on your machine. The first time that happens the window asks once whether to send crash reports; you can change the answer in Settings → Reports, or with moxivue feedback --crash on or off.

A crash report holds exactly this and nothing else: the MoxiVue version, the package (desktop or server), the system name and processor type (for example "Ubuntu 24.04, x86_64"), which part stopped (agent, window or command line) and the place in the program (a file name and line number in our program or a library it uses). Settings → Reports shows the last one that was sent.

What happens next

We read every report. We reply only if you gave an address, and we use the address for nothing else. Problems we can reproduce are tracked privately and named in the notes of the version that fixes them, which the app shows before you accept an update.