Skip to content
GitTree
العربية
Troubleshooting

A keyring or SSH request failed

GitTree keeps account tokens, its sign-in and remembered SSH passphrases only in your system keychain: the macOS Keychain, Windows Credential Manager, or the Secret Service (GNOME Keyring or KeePassXC) on Linux. When the keychain says no, GitTree asks you to allow access and try again; it never falls back to a file.

FreeUpdated

Works in GitTree Free: every local Git feature, once you are signed in.

On this page
  1. Before you start
  2. Where to find it
  3. Steps
  4. Expected result
  5. If something goes wrong
  6. Questions
  7. Related

Before you start

  • Your system account password, to unlock or allow the keychain.

Where to find it

  • The message GitTree shows; Preferences › SSH for passphrases.
ActionmacOSWindows and Linux
Preferences⌘,Ctrl+,

Steps

  1. Allow access

    When macOS asks whether GitTree may use a keychain item, choose Always Allow. Then press Ask again in GitTree.

  2. Unlock the keyring on Linux

    Make sure a Secret Service provider (GNOME Keyring or KeePassXC) is running and unlocked in your session, then try again.

  3. Stop repeated passphrase prompts

    Turn on Remember key passphrases in Preferences › SSH, or Use the SSH agent if your agent already holds the key. Forget Remembered Passphrase removes one.

Expected result

GitTree reads what it keeps in your keychain, and SSH stops asking every time.

If something goes wrong

“GitTree could not read a connected account from the macOS Keychain.”

Allow access when macOS asks, or reconnect the account so a new item is written.

Questions

Can GitTree store tokens in a file instead?

No. Secrets live only in the system keychain, never in files, git config or the app’s window.

Related