"Write access is required for uploading LFS objects" when pushing to repo? Edited


My colleague & I have been happily using SourceTree (OSX 2.6.3) to push/pull to our repo (with LFS) hosted on bitbucket for the past month or so, however yesterday my colleague suddenly started getting the following error when trying to push:

git -c diff.mnemonicprefix=false -c core.quotepath=false -c credential.helper=sourcetree -c lfs.customtransfer.bitbucket-media-api.path=/Applications/SourceTree.app/Contents/Resources/git_local/git-lfs/git-lfs-bitbucket-media-api push -v --tags origin refs/heads/master:refs/heads/master
Pushing to https:<repo>
batch response: Write access is required for uploading LFS objects
error: failed to push some refs to 'https:<repo>'
Git LFS: (0 of 9 files) 0 B / 26.51 MB
Completed with errors, see above


Pulling works fine, just not pushing.  Nothing obvious has changed, & the LFS is reporting it still has over 2GB of space available.  I've spent most of today googling for answers but so far have had no luck.  Any ideas?


3 answers

This widget could not be displayed.

I just got the same error, yesterday as well.  I had stashed some local changes, pulled from the repo, and then applied my stash and committed.  When I try to push the commit, I see the same error.  Haven't been able to figure out what's going on yet.  Hoping someone has an idea on this.  Thanks for the post.

This widget could not be displayed.

So, haven't been able to find a solution with SourceTree.  But, I downloaded GitKraken, opened the repo, and was able to push successfully with that.  Just thought I'd let anyone know that was having the same issue.


This one is also not working. Still getting the same error.

This widget could not be displayed.

This error have also begun popping up on different machines in our office. We haven't identified the cause of this issue, but we figured out a temporary work around by switching from HTTPS to SSH. We don't appreciate this, but it is a temporary workaround until we figure out what is causing it.

Suggest an answer

Log in or Sign up to answer
Community showcase
Published Aug 21, 2018 in Bitbucket

Branch Management with Bitbucket

As a project manager, I have discovered that different developers want to bring their previous branching method with them when they join the team. Some developers are used to performing individual wo...

1,306 views 8 11
Read article

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you