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

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


1 badge earned


Participate in fun challenges

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


Gift kudos to your peers

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


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!


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
Community Members
Community Events
Community Groups

gitlfs batch response: Post https://../info/lfs/objects/batch: ..proxyconnect tcp: tls: first record

I have a bitbucket server git repo with LFS turned on. Yesterday I activated the use of LFS for a number of file types in my local clone and pushed all changes, including .gitattributes in the repo root.

A colleague of mine pulled the changes, executed git LFS install but now finds in his clone the LFS link files instead of the real files.

Another git pull made no difference, and a git LFS pull gave him

$ git lfs pull
batch response: Post https://<bitbucket-server>/scm/<proj>/<repo>.git/info/lfs/objects/batch:
...proxyconnect tcp: tls: first record does not look like a TLS handshake
error: failed to fetch some objects from

Unfortunately there is no hint on any git lfs info page what this means - and how to fix it.

1 answer

I get the same problem too, did you solve the problem later?

- git lfs pull

it shows

- proxyconnect tcp: tls: first record does not look like a TLS handshake

Appreciate it if you have any updates.

Suggest an answer

Log in or Sign up to answer

Atlassian Community Events