Gerrit code review plugin for Git Extensions does not let me push
<p>I have a gerrit instance setup, where i can push with git, no problem.</p>

<p>The only problem is when I am trying to do the same from Git Extensions.
Then I get this error:</p>

<p><a href="https://i.stack.imgur.com/zYGhn.png" rel="nofollow noreferrer"><img src="https://i.stack.imgur.com/zYGhn.png" alt="enter image description here"></a></p>

<p>The .gitreview file is as follows:</p>

<pre><code>[gerrit]
host=193.27.84.155
port=29418
project=IMAGO.git
defaultbranch=master
</code></pre>

<p>On the git-review site I read: </p>

<blockquote>
  <p>Required values: host, project</p>
  
  <p>Optional values: port (default: 29418), defaultbranch (default:
  master), defaultremote (default: gerrit).</p>
  
  <p>Notes</p>
  
  <p>Username is not required because it is requested on first run Unlike
  git config files, there cannot be any whitespace before the name of
  the variable. Upon first run, git-review will create a remote for
  working with Gerrit, if it does not already exist. By default, the
  remote name is ‘gerrit’, but this can be overridden with the
  ‘defaultremote’ configuration option. You can specify different values
  to be used as defaults in ~/.config/git-review/git-review.conf or
  /etc/git-review/git-review.conf. Git-review will query git credential
  system for gerrit user/password when authentication failed over
  http(s). Unlike git, git-review does not persist gerrit user/password
  in git credential system for security purposes and git credential
  system configuration stays under user responsibility.</p>
</blockquote>

<p>What can I do?</p>

<hr>

<p>EDIT: Ok, so after wandering the internet for quite some time, I decided to go and fetch the latest version of Python and reinstall git-review. Amazingly, this worked. However, now putty is complaining about the private key, connection refused etc. Just to keep everyone updated, if all the work is done via the bash, everything works like a charm. I will get back to my searches and will keep you all posted.</p>

<hr>

<p>EDIT: Well, I have just changed the ssh client to OpenSSH instead of PuTTY and everything works nicely now. If this can help anyone, I am glad.</p>