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

[klausisbruch]

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 
'https://<bitbucket-server>/scm/<proj>/<repo>.git/info/lfs'

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

[沈文振]

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.