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
4,298,096
Community Members
 
Community Events
165
Community Groups

Permanently losing authorization to a branch, but not the repo.

Edited

Hello everyone!  I think this is a weird one, and I'll try to be thorough.

I and some other developers on the team have this ongoing issue with our company Bitbucket accounts.  It's been an issue for over six months, and IT is stumped.

We have three repositories and six submodules, and at least two or three times a month, a developer will lose authorization on a branch they've already pushed a few commits to.   Once this authorization error happens:

  • That developer can't commit to that branch any more, but other developers can.
  • Trying to push to that branch via Sourcetree (v3.3.9) just shows the progress bar until you quit, no progress actually happening.
  • Trying to push to that branch via bash, it will ask you to log in 2 or 3 times, then fail with "batch reponse: Authorization error" and "Check that you have proper access to the repository", and "error: failed to push some refs to [$repo]", which is odd since we can still access other branches just fine.
  • Windows pops up multiple OpenSSH "Authenticate" windows, and neither logging in or closing it gets rid of it... it just keeps popping back up.  (Virus check was clean.)
  • The developer still has normal access to other repos and branches on the same repo, so it's only that one branch that suddenly rejects access, even if it allowed several commits a few minutes earlier.

So far, the only solution has been to create a new branch and bring your local changes over, or to re-clone the project completely.  None of the developers have this issue with any other Bitbucket accounts or repositories - it's limited to just the ones run by our company.  We've re-installed everything multiple times, including LFS, and tried different devices as well, and we think the issue is tied to the account, not the device.

LFS is definitely related, but again, it's hard to figure out how since there will be several successful commits of LFS assets to a branch before this error appears.

If it matters:  Even when things aren't blocked like this, some developers still have to log in three or four times during one commit. 

 

Here's the bash when I try to push the latest changes:

bitbucket 4.png


Here's the OpenSSH window that it opens multiple copies of, even when you close it.  (In the Task Manager, we can see multiple instances of it running, as "Git for Windows (32 bit)")
bitbucket 2.png

 

Thanks for taking a look.  Sorry if I missed any details, it's been difficult to diagnose.

 

0 answers

Suggest an answer

Log in or Sign up to answer
TAGS
Community showcase
Published in Bitbucket

Git push size limits are coming to Bitbucket Cloud starting April 4th, 2022

Beginning on April 4th, we will be implementing push limits. This means that your push cannot be completed if it is over 3.5 GB. If you do attempt to complete a push that is over 3.5 GB, it will fail...

2,223 views 2 9
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you