Skip to content
TaktSignal

Docs / Look after it · Community Alpha

Troubleshooting

Start with the Control Center (the TaktSignal icon opens it). Every problem is shown with a plain title, what it means, whether anything was changed, and buttons for what to do next. If nothing here helps, export diagnostics and report it.

TaktSignal does not open

  • Clicking the icon seems to do nothing — wait 30 seconds; the first start prepares the database. Then click again. A second start never runs TaktSignal twice.
  • The browser says the page cannot be reached — TaktSignal stopped. Click the icon again. If it keeps happening, export diagnostics.
  • A page says “Open TaktSignal from your applications menu” — the Control Center only opens through the icon or menu entry (a one-time sign-in link protects it). Use the icon.
  • Sign-in says “Cross-origin request blocked” — open TaktSignal with the Control Center's Open TaktSignal button instead of typing an address.

macOS: “Apple could not verify TaktSignal is free of malware”

Expected for the unsigned Community Alpha. Approve this one app in System Settings → Privacy & Security → Open Anyway — step by step in the macOS guide. Needed once per downloaded copy. Never turn off Gatekeeper.

Windows: “Windows protected your PC”

Expected for the unsigned experimental build. Check the SHA-256, then More info → Run anyway for this file only (Windows guide). Never turn off SmartScreen or Defender.

“Something needs attention” during the system check

Each failed check says why:

  • Not enough free disk space — 2 GB is needed.
  • TaktSignal cannot find a secure password store on this computer — Linux: sign in to a desktop session with GNOME Keyring or KWallet (servers without a desktop have none). macOS: the login keychain must be unlocked. TaktSignal will not store secrets in a plain file.
  • Program files missing or damaged — reinstall from taktsignal.cloud/download.

Database unavailable

TaktSignal's local database did not start / was not shut down cleanly → Help & diagnostics → Repair TaktSignal (Repair). Database files are missing → restore a backup. Your data is never silently replaced by an empty database.

Application unavailable

The TaktSignal application did not start → Repair. If it persists, export diagnostics.

Background updates unavailable

Background updates stopped means TaktSignal still opens, but it no longer refreshes ERPNext data on its own. → Repair. Data stays visible but grows stale until fixed — the freshness line shows it.

ERPNext unreachable

Cannot find this ERPNext server / refused the connection / did not answer in time / could not reach ERPNext — check the address in Control Center → Connection, that this computer can open ERPNext in a browser, and VPN or proxy settings. Cannot securely verify this ERPNext server — the certificate is not trusted by this computer; ask IT to install the company certificate. TaktSignal never ignores certificate errors.

Credentials rejected

ERPNext rejected the API credentials — the keys were regenerated, mistyped or the Reader was disabled. Generate keys again in ERPNext and enter them in Control Center → Connection.

Write-enabled ERPNext account

This ERPNext account has write permissions — remove every role except TaktSignal Reader and make sure the role has only Read ticked. Details. There is no way to skip this.

Unsupported ERPNext version

TaktSignal has been exercised with ERPNext 15 and 16. Other versions connect with a not validated warning. You can continue, but expect gaps — please report what you see.

Sync failed or data is stale

See Sync and freshness. The Integrations page lists each run with its error. Stale data lowers the confidence of the alerts that depend on it.

Job Card or Stock Entry unavailable

The Reader cannot read that document type. TaktSignal keeps working with reduced capability — Job Card: progress from work orders only, lower timing confidence; Stock Entry: no material reconciliation. Add Read permission for the document type to the TaktSignal Reader role and click Test again (Control Center → Connection).

Backup problems

  • The backup could not be created — check free disk space and retry.
  • This file is not a usable TaktSignal backup — it is damaged or not a TaktSignal backup; nothing changed.
  • This backup comes from a newer TaktSignal version — update TaktSignal first.
  • The restore did not complete — TaktSignal returned to the data you had before; nothing was lost.

Updates

  • The update could not be downloaded — internet connection or proxy; nothing was installed.
  • This update could not be verified — nothing was installed. Download the new version from the website.
  • The update did not start correctly and was undone — you are on the previous version. If asked, restore the before update backup.

Reinstall or start over

Reinstalling over an existing installation keeps your data. To start completely fresh: uninstall with Remove all TaktSignal data (Uninstall), then install again.

Where things are

Logs: macOS ~/Library/Logs/TaktSignal, Windows %LOCALAPPDATA%\TaktSignal\logs, Linux ~/.local/state/taktsignal/logs (the recent part is also in Control Center → Advanced → Logs). Logs have passwords and keys removed, but may contain ERPNext document numbers — review before sharing them. Prefer the diagnostics file.