FGIT — support

Start with a controlled workspace.

FGIT can run entirely on your Mac or connect to an FGIT server you operate.

First launch on macOS

  1. Open FGIT and create an administrator password of at least 12 characters.
  2. Choose This Mac to start the embedded local server.
  3. Sign in with the administrator account created during setup.
  4. Create or select a case before importing or collecting evidence.

Local data is stored in the app’s container. Keep a backup of the workspace before experimenting with migrations or disk changes.

Connect to a remote server

  1. Choose Remote server from the connection screen.
  2. Enter the HTTPS URL of the FGIT server, without a username or password in the URL.
  3. Save the connection, then sign in with an account on that server.

For a server exposed to the internet, use HTTPS, a strong JWT secret, a unique administrator password, firewall rules, and regular backups. Do not expose a development server directly to the public internet.

Common problems

The local server does not start

Quit and reopen FGIT, check that another service is not using the local port, and confirm the app has permission to use its container. If the problem persists, include the macOS version and the time of the failed start in your support email.

The remote connection fails

Check the URL, DNS, VPN, TLS certificate, and firewall. The server should expose the FGIT API and return its readiness response. Confirm that the account exists on that server.

A case or artifact is missing

Check that you are connected to the intended server and case. Local and remote workspaces are separate; switching connections does not copy evidence between them.

Backups and recovery

Back up the configured FGIT data root and database using the procedures appropriate to your deployment. Preserve evidence and its metadata together, test restoring to a separate workspace, and document who can access the backup.

Contact support

Email support@tkgdata.com. Please include the FGIT version, macOS version, local or remote mode, and a redacted description of the error. Never send passwords, JWTs, private keys, or unredacted evidence.