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

A remote authentication attempt failed

Git signs in to a remote with your own credential helper or SSH key first. … needs you to sign in. means nothing answered; … refused the credentials sent for this repository. means what was sent is no longer valid or not allowed. Fix the credential Git uses; a connected account fills in only when your helpers have nothing, or when you choose it for a repository.

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

  • Know whether the remote is HTTPS (https://…) or SSH (git@…): Copy Remote URL shows it.

Where to find it

  • The error after a fetch, pull or push; the Activity Log has the full git output.
ActionmacOSWindows and Linux
Fetch again⌘⇧FCtrl+Shift+F

Steps

  1. For HTTPS remotes

    Update the password or token stored in your credential helper (Git Credential Manager, macOS Keychain). Many hosts need a personal access token instead of your password.

  2. For SSH remotes

    Test the key in Preferences › SSH › Test a connection. If the host does not accept it, add your public key there (Configure SSH).

  3. Try again

    Fetch again. With a connected account and Pro, you can also choose the account for this repository (Authentication and credentials).

Expected result

Fetch, pull and push work again with a credential the host accepts.

If something goes wrong

“Git could not ask you to sign in to …”

The helper that shows GitTree’s sign-in prompts is missing. Reinstall GitTree.

“Passing your connected accounts to Git is part of GitTree Pro.”

Your own SSH key or credential helper keeps working on Free; set one of them up.

Questions

Does GitTree store my Git password?

No. Passwords stay with your credential helper, and account tokens only in your system keychain.

Related