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

[V0odo0]

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?

[Liang Peng]

I solved this problem by the following command:

git config --add lfs.url http://XXX@bitbucket.org/XXX/repo.git/info/lfs/objects/batch

Pay attention to the http protocal.

this article give me some inspiration:

manage_large_binaries_with_git_lfs 

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:

[Daniel Todorov]

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