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

Getting proxy authentictaion required error using Git LFS Pull

Manisha.Natambe January 28, 2019
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
lucfri February 26, 2019

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

AnthonyMaidment June 22, 2020

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
AUG Leaders

Atlassian Community Events