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

Failing to fetch git lfs assets after cloning project

One of the team's developers are having problems pulling down the git lfs content from a bitbucket repository after cloning the repository.

The repository is accessed via the https protocol along with app password. The repository is able to successfully cloned however all of the assets marked to be tracked by git lfs are marked as changed. 


If we try to discard the changes, we get the following response from git.

batch response: Repository or object not found:
Check that it exists and that you have proper access to it
error: failed to fetch some objects from ''

From reading that message, it appears to be an authentication issue but if there was a successful clone of the main repository, you'd think the authentication would also be valid for the lfs content.

When inspecting these assets, the change to the files resembles that of an asset deletion.

This issue is only affecting one member in the team and other team members have no problems pulling down the lfs tracked assets. This member also in the same user groups on bitbucket for access to repositories and permissions.


We tried duplicating the project and uploading a new copy of the repository to bitbucket and the same issue occurs when they clone the repository.


The final confusing part, the user has been able to successfully clone other repositories with lfs tracked assets and have no problems pulling down these assets.

1 answer

1 accepted

0 votes
Answer accepted
Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 08, 2022

G'day Nick!

If the user is having issues fetching lfs content over HTTPS, I would suggest that they first ensure that the remote URL has been updated to include the App Password to avoid any potential authentication issues:

git remote set-url origin

If the clone command is using the App Password, but their remote URL is not updated - this would explain why they are able to clone but not able to pull.

Once this is done, I would suggest having them also ensure that git lfs is definitely installed on their local repository by running the following command, as if it is not - any git lfs commands will not work as GIT will not understand how to pull the data:

git lfs install

Once the above steps have been performed, ask them to try to perform the git lfs fetch without the lfs path included - as this is not required and can cause issues when trying to locate the remote repo location:

git lfs fetch origin main

Hope this helps, let me know if there are any issues.


- Ben (Bitbucket Cloud Support)

We found that we were missing the username in the git path.

The path we had that was causing the problem. 

The path we used that resolved the problem 

Atlassian Team
Atlassian Team members are employees working across the company in a wide variety of roles.
Jun 15, 2022

Hey Nick!

Awesome, glad to hear that this has helped you out! :D


- Ben (Bitbucket Cloud Support)

Like nick_maunder likes this

Suggest an answer

Log in or Sign up to answer
AUG Leaders

Atlassian Community Events