Bitbucket does not support Git's legacy HTTP transport protocol when using Git LFS
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Problem
When pushing to Bitbucket Server and using Git LFS, the following error is returned from the Git client:
$ git lfs push origin master --all
Invalid request from host 192.168.1.10: Note that Bitbucket does not support Git's legacy HTTP transport protocol.Cause
Cause #1
The Git client has been configured to use the legacy "Original v1 API", which can be caused by a bug in the LFS client (see Fix fallthrough when git-lfs-authenticate returns an error #909). This will set the following in .git/config:
[lfs]
batch = falseThis tells Git LFS to not use the Batch API and just use the Legacy API. Since the Legacy API is due for removal and inefficient, it's not implemented in Bitbucket Server.
Cause #2
The Base URL for Bitbucket Server is set incorrectly.
Resolution
Cause #1
Remove the batch = false configuration from the Git config.
Cause #2
Under Administration >> Server Settings set the Base URL to the correct value.