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 pullbatch 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?
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
I solved this problem by the following command:
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.
Post <URL>/info/lfs/objects/batch: dial tcp IP: getsockopt: connection refused
This behaviour is caused by Git LFS using HTTPS connections by default when a lfsurl is not set in the Git config.
lfsurl
To prevent this from happening, set the lfs url in project Git config:
It looks like you're new here. Sign in or register to get started.
