Check in Preferences Authentication to confirm that your SSH settings are correct.

Edit remotes in the left ref panel to ensure push and pull urls are set and in the correct format

Expected use of SSH config — GitKraken does not currently respect your SSH config and cannot make use of any remote server nicknames or identities.

You can either load your SSH key directly into GitKraken or use your system’s SSH agent to authenticate with your remote.

Proxy configuration

GitKraken supports proxies for Windows, OSX, and Linux. GitKraken should recognize your proxy settings by default, however please review the additional instructions below if you are using an authenticated proxy such as basic, NTLM, Negotiate, or Digest.

Windows

For Windows users, your Windows machine will prompt for your proxy credentials on GitKraken’s behalf. Enter the credentials to complete the proxy configuration with GitKraken.

OSX

If you’re using an authenticated proxy on OSX, GitKraken will directly ask for the proxy credentials. Enter the credentials to complete the proxy configuration with GitKraken.

Linux

If you are using an authenticated proxy on Linux, Gitkraken will directly ask for the proxy credentials. Additionally, you will need to run GitKraken with the command line flag:

--proxy-server=10.200.0.1:8080

where 10.200.0.1 and 8080 are the proxy IP and proxy port respectively. Without this flag, OAuth integrations are subject to fail.