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

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Getting proxy authentictaion required error using Git LFS Pull Edited

Hi Team,
git-lfs/2.6.1 (GitHub; windows amd64; go 1.11.1; git dc072c3e)
git version 2.20.1.windows.1
We have Git LFS Repository , We are trying to downloads lib files from Git LFS Pull
I am getting error as batch response: Post https://bitbucket.git/info/ lfs/objects/batch: Proxy Authentication Required
so How to fix this issue.
Using corporate proxy required system credentials to connect.
We are setting this proxy with user details.
Using set HTTP_proxy also git config http.proxy but stills when we do git lfs pull facing batch response proxy authentication required.
For normal git we are able to connect. But for git LFS repo we are continuously getting proxy issue.

1 answer

1 accepted

0 votes
Answer accepted

I have the exact same problem when cloning/pushing on Git LFS enabled repositories. Git works as expected trough the proxy, but somehow Git LFS is not picking the right configuration. I tried to set environment variables as well (HTTP_PROXY and HTTPS_PROXY) without luck.

Is there any additional setting for Git LFS in order to make it work behind a corporate proxy?

Microsoft Windows 10 Enterprise 1709 (16299 .904)

git-lfs/2.6.1 (GitHub; windows amd64; go 1.11.1; git dc072c3e)
git version 2.20.1.windows.1

ENV:
LocalWorkingDir=C:\Users\***
LocalGitDir=C:\Users\***
LocalGitStorageDir=C:\Users\***
LocalMediaDir=C:\Users\***
LocalReferenceDirs=
TempDir=C:\Users\***
ConcurrentTransfers=3
TusTransfers=false
BasicTransfersOnly=false
SkipDownloadErrors=false
FetchRecentAlways=false
FetchRecentRefsDays=7
FetchRecentCommitsDays=0
FetchRecentRefsIncludeRemotes=true
PruneOffsetDays=3
PruneVerifyRemoteAlways=false
PruneRemoteName=origin
LfsStorageDir=C:\Users\***
AccessDownload=none
AccessUpload=none
DownloadTransfers=basic
UploadTransfers=basic
GIT_CONFIG_PARAMETERS='filter.lfs.smudge=' 'filter.lfs.required=false' 'color.branch=false' 'color.diff=false' 'color.status=false' 'diff.mnemonicprefix=false' 'core.quotepath=false'
GIT_DIR=C:/Users/***
GIT_EXEC_PATH=C:/Program Files/Git/mingw64/libexec/git-core
GIT_PAGER=cat

Why is this accepted as the solution? It's a "me too" comment, with additional information on the environment that was producing the issue.

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Powering DevOps with Bitbucket Server & Data Center

Hi everyone, The Cloud team recently announced 12 new DevOps features that help developers ship better code, faster   ! While we’re all excited about the new improvements to Bitbucket ...

1,886 views 0 7
Read article

Community Events

Connect with like-minded Atlassian users at free events near you!

Find an event

Connect with like-minded Atlassian users at free events near you!

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you