Showing results for 
Search instead for 
Did you mean: 
Sign up Log in

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root


1 badge earned


Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!


Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.


Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!


Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
Community Members
Community Events
Community Groups

Every Interaction has HttpRequestExeption Error


Have a new repo and configured with LFS.  I've been able to do normal git operation to clone, add, commit, push, etc... and I get the the expected results so far.  However, there is always a complaint in the details that seems to be associated with LFS but I'm not sure.  A sample of the error message follows here:

git -c diff.mnemonicprefix=false -c core.quotepath=false -c lfs.customtransfer.bitbucket-media-api.path=git-lfs-bitbucket-media-api push -v origin refs/tags/FUS
fatal: HttpRequestException encountered.
   An error occurred while sending the request.

Other detailed entries regarding git operations have no errors so the the core git functions are fine.  I'm using ssh auth and there are no complaints with SourceTree or shell based repo interactions.

I'm reluctant to just keep plugging along even though things "seem" to be working fine just to get bitten down the road.  Sincere thanks in advance for any advice.

Best regards,



2 answers

1 accepted

1 vote
Answer accepted
minnsey Atlassian Team Sep 06, 2018


I believe that error is coming from the Git Credential Manager. You can try and confirm that by running the same command in the Terminal/Command line, first having set the following environment variable 


And then post up the trace?

Can I check which git host you are using Bitbucket, GitHub etc?

I've done some more testing. I can reproduce similar behaviour if I'm using a Git install that includes a broken Git Credential Manager for Windows (GCMW), essentially v1.16.1 and v1.16.2.

Sourcetree can detect the broken versions of Git Credential Manager and force the use of a working copy, v1.17.1, using the following parameters with Git calls

-c credential.helper= -c credential.helper="C:/Users/mminns/AppData/Local/ATLASS~1/SOURCE~1/GIT_EX~1/GIT-CR~1.EXE"

However I suspect this override isn't being carried through to git-lfs which is then calling Git without the overrides and uses the broken Git Credential Manager which fails to authenticate.

Until the fixed version of Git Credential Manager is shipped with a new Git for Windows release which is bundled with a new Sourcetree release please use the following work around.

Work Around

1) thank for digging in on this - really appreciate your effort/support

2) using bitbucket

3) if I've followed directions correctly, after setting GCM_TRACE=1, I executed the command that appears in the logs that generates the complaint and I initially get the following

fatal: HttpRequestException encountered.
   An error occurred while sending the request.

and then am prompted for my bitbucket password twice.  I respond with my bitbucket password and the command continue and succeeds.  Let me know if this is what you were looking for.

4) Could use a little more coaching on the work around proposed as the GCMW-1.17.1 installer insists on installing git 2.17.0.  The manual install instructions using the zip don't have a case for an existing version of git.  Do you have any advice?

minnsey Atlassian Team Sep 07, 2018

The .exe installer for the GCM should find any git installs in the PATH or the standard program files locations. It only offers to install Git if it can't find it. I'm guessing you have installed in a different location?

You can re-direct the installer to your own Git install. See and using the zip installer, extract the GCM files and then run

>git-credential-manager.exe deploy --path <installation_path>

There was an issue as I had installed Git 2.18...  as a regular user so it was installed in a local dir and while you provided information on working around that, did the following instead:

I removed everything (git, gcmw, sourcetree), removed prefetch files referencing the local location, cleaned up an LFS addition to my local path variable, and then reinstalled git 2.18..., GCMW, and LFS with Admin permissions.  Setup Sourcetree and no more errors on pushes!

This will get me going now and I'll deal with setting this up as a regular user when I get ready to move to my customer's systems.

Thank you very much!

Adding this from the Git options tab in case it's helpful:

SourceTree Git Config.PNG

0 votes
bgannin Atlassian Team Sep 05, 2018

Hi Kurt,

Thank you for noting this, it's a reasonable idea to avoid any LFS operations until we confirm the message is harmless. Please file a ticket (SRCTREE or SRCTREEWIN depending on your OS) and we'll take it from there.


Brian Ganninger
Product Manager, Sourcetree

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events