Troubleshoot Git LFS in Bitbucket
This page describes how to troubleshoot problems you may experience when using Git LFS with Bitbucket.
General Git LFS issues
Have you installed the Git LFS client on your local machine?
Each person who works with the repository has to have the Git LFS client installed on their local machine.
See Use Git LFS with Bitbucket for instructions.
Has Git LFS file tracking been set up, and has the .gitattributes file been pushed to the repo?
The repository needs to have file tracking set up, and the updated .gitattributes file should have been pushed to the repo.
Other people who subsequently work with the repository should see that .gitattributes file in their local clone of the repo.
See Use Git LFS with Bitbucket for instructions.
Have you checked that you have enough storage in your Bitbucket account?
Bitbucket will prevent you from pushing LFS files to the repository if doing so would exceed the storage limit for your account.
You can check the current storage used by your account by choosing Personal settings > Git LFS from the avatar menu in Bitbucket.
See Storage policy for Git LFS with Bitbucket for details.
Specific Git LFS errors
The Git LFS file is missing
The LFS pointer file exists in the repo, but the target file in the remote store can't be found. A File missing error will be returned, letting you know that your file may not have been uploaded correctly.
In a terminal, you may see a 404 message similar to this:
Git LFS: (0 of 1 files, 1 skipped) 0 B / 1024 B, 1024 B skipped
[404] Object does not exist on the server
[ee62792aacdfe08a6f5437...8dc4eb6973d86c74c1a273] Object does not exist on the serverPossible causes | Actions you can take |
|---|---|
The file storage server may be down. | Try again later. |
The file was not correctly uploaded. This can happen if Git LFS is incorrectly configured when you try to upload the file. | If you have access to the original file, try uploading it again. For example, restoring Unfortunately, you can't do anything if you don't have the original file. |
Error when pushing Git LFS file to Bitbucket
Pushing a large Git LFS file to Bitbucket.org times out and fails.
In a terminal, you may see a message similar to this:
Git LFS: (0 of 1 files) 1.60 GB / 1.60 GB
http: Put https://media-api.atlassian.io/upload/7cd73528-28e4-4c45-92a5-e6ddbf52a75e/binary?hashAlgorithm=sha2...: EOF
error: failed to push some refs to 'git@bitbucket.org:account/some_repo.git'Possible causes | Actions you can take |
|---|---|
Pushing a really large file (multiple gigabytes in size) times out. | Try increasing the LFS time limit with the following command: |
Error when pushing really large or very many files to Git LFS using SSH
Pushing really large files or a lot of files to Git LFS times out and fails when using SSH.
In a terminal, you may see a message similar to this:
Git LFS: (0 of 1 files) 1.60 GB / 1.60 GB
http: Put https://media-api.atlassian.io/upload/7cd73528-28e4-4c45-92a5-e6ddbf52a75e/binary?hashAlgorithm=sha2...: EOF
error: failed to push some refs to 'git@bitbucket.org:account/some_repo.git'Possible causes | Actions you can take |
|---|---|
Time out using SSH and failed to push |
|