10

My firewall is configured to deny all inbound and outbound traffic unless a rule says otherwise.

Firewall Profile Screenshot

This answer suggests making rules for git.exe, sh.exe, and ssh.exe. So I did. Even bash.exe.

Firewall Rules Screenshot

Still when I run git pull I see:

fatal: unable to access 'https://joncom@bitbucket.org/joncom/my-repo.git/': Failed connect to bitbucket.org:443; No error

If I allow outbound connections by default, everything works.

Firewall Profile Screenshot

What rule am I missing?

Community
  • 1
  • 1
Joncom
  • 1,985
  • 1
  • 18
  • 29

4 Answers4

24

I needed to add a rule for git-remote-https.exe because I'm authenticating via HTTPS, not SSH.

On new versions of git, this is located at: C:\Program Files\Git\mingw64\libexec\git-core\git-remote-https.exe.

Edit: In fact I disabled the rules for git.exe, sh.exe, ssh.exe, and bash.exe, and still everything works, so they seem unnecessary for my purposes.

Li-aung Yip
  • 12,320
  • 5
  • 34
  • 49
Joncom
  • 1,985
  • 1
  • 18
  • 29
2

When using:

git submodule update

I had to allow $GIT_BASH_LOCATION/usr/bin/ssh.exe through the firewall. In almost all other cases it is not used.

0

I had the same problem but since I don't have a git-remote-https.exe I needed to open the Ports for git. You need to open the ones described in this question here.

Community
  • 1
  • 1
Wagawonga
  • 31
  • 4
0

If you're using Git for Windows and Putty, you should allow plink.exe

anno
  • 5,970
  • 4
  • 28
  • 37