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

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

Avatar

1 badge earned

Collect

Participate in fun challenges

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

Challenges
Coins

Gift kudos to your peers

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

Recognition
Ribbon

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!

Leaderboard

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
4,456,659
Community Members
 
Community Events
176
Community Groups

Pulling LFS files error: Check that you have proper access to the repository

Today I'm unable to pull my LFS files with the following error:

git -c diff.mnemonicprefix=false -c core.quotepath=false --no-optional-locks -c lfs.customtransfer.bitbucket-media-api.path=git-lfs-bitbucket-media-api lfs pull
batch response: Authorization error: https://XXX@bitbucket.org/XXX/ptc-pro-tactical-constructor.git/info/lfs/objects/batch

Problem is related to LFS files only. Everything was fine just yesterday. The only thing that was changed is upgraded plan from free to premium. 

There is a workaround or should be considered as bug?

2 answers

I solved this problem by the following command:

 

Pay attention to the http protocal.
this article give me some inspiration:

If you push a LFS object to a project and you receive an error similar to: Post <URL>/info/lfs/objects/batch: dial tcp IP: getsockopt: connection refused, the LFS client is trying to reach GitLab through HTTPS. However, your GitLab instance is being served on HTTP.

This behaviour is caused by Git LFS using HTTPS connections by default when a lfsurl is not set in the Git config.

To prevent this from happening, set the lfs url in project Git config:

We are facing the same issue from Friday, when our Bamboo server try to checkout our repos. LFS is failing with:

 

batch response: Authorization error:  https://XXX@bitbucket.org/XXX/repo.git/info/lfs/objects/batch

 

Nothing is changed from our side.

Bamboo version: 7.0.6

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events