Troubleshooting

An audit could not be completed

Damdit shows the reason. Your previous results stay current. Common causes:

• The website didn’t respond. Check that it’s online and that the address in Project settings is right, then choose Try Again.
• The website blocks automated visitors. Some firewalls block requests that aren’t from a regular browser. Allow Damdit’s requests, or audit a staging address.
• The computer went to sleep. Turn on background audits so audits keep the computer awake.

The result says “Limited”

Part of the website or an area couldn’t be measured. Open Coverage: every gap says why and what helps, for example connecting PageSpeed Insights for Performance or Search Console for Indexability.

Run audit is unavailable

Only one audit runs at a time across all projects. Wait for the other one, or stop it.

A licence is needed

See Licence and trial. If Damdit says it hasn’t been able to check your licence, connect to the internet and choose Check Now in Settings → Account. If it says your clock is wrong, correct the date and time.

“Secure storage is not available” on Linux

Damdit stores tokens and keys only in the system’s secure storage. Start a secret service, such as GNOME Keyring or KWallet, log out and in again, then try again.

The damdit command or MCP doesn’t answer

• runner_unavailable (exit 3): Damdit isn’t running. Open it, or turn on background audits to use the command with the window closed.
• damdit: command not found: open Settings → AI Tools → Command Line. If it isn’t installed, choose Install. On macOS and Linux, add ~/.local/bin to your PATH as Damdit shows.
• api_disabled (exit 6): the command or MCP is turned off in Settings → AI Tools.
• review_required (exit 6): run the project’s first audit in the app and start it after reviewing the plan.
• An AI app doesn’t see Damdit’s tools: restart the app after adding Damdit. In Settings → AI Tools, check that the app shows Added.

damdit diagnostics shows the versions, the AI Tools switches and the latest audits.

Damdit quit unexpectedly

At the next launch Damdit offers to send a crash report by e-mail. Nothing is sent until you send the e-mail yourself, and you can read and edit it first. It names the app version and your system, when the session started, when Damdit was last seen running and what it was doing (for example “Packing a saved audit”), and on macOS a one-line summary of the system’s crash report, such as “JavaScript out of memory”. It never contains website addresses, project names, file paths or your account.

Get help

Settings → About & Support → Contact Support opens an e-mail to support@damdit.com with diagnostic information, with personal details removed. Review it before you send it.