1. Bitbucket
  2. Public Issue Tracker
  3. master
  4. Issues


Issue #4020 resolved

Http error 403 on command line when over plan limit for http (BB-6305)

created an issue

When pushing over https, users may see an error similar to the following:

The requested URL returned error: 403 while accessing https://{username}@bitbucket.org/{username}/{repo slug}.git/info/refs
fatal: HTTP request failed

This is a bug. Instead the message should tell users that the account they are trying to push to is over their plan limit.

Comments (17)

  1. sushilchoudhari reporter

    Now i am getting a different error

    $ git pull Enter passphrase for key '/home/ec2-user/.ssh/id_rsa': conq: the account owner 'madhurk' has exceeded their user limit - write access is disabled to the repository 'msg_ui'. fatal: The remote end hung up unexpectedly

    but we have only 4 users in the branch, why are we seeing this error , i think we were allowed 5 users with free account


  2. Dylan Etkin


    I have opened this as a support request, you should receive an email with my response there.

    Since this is related to your repo and I may need private information I would rather track this through support.



  3. Carl Rannaberg

    This error is caused by the repo owner exceeding it's limit. Limit on users which are given access to their repos. When exceeding this limit, write access is disabled to everyone else in the repo. Ask repo owner to remove one/some of the users from repo.

    This is huge UX fail. It should notify repo owner about exceeding this user limit when adding users to repos.

  4. Aaron Ransley

    Resolved issue on my end.

    Had to do with some kind of cutover on BitBucket's backend, wherein team account logins can no longer be used for HTTPS auth in a URL. Once I updated my Git client to a 2.x revision, the 403 turned into a more verbose message explaining this change.

    After creating a new user within the team and assigning a password, I was able to provide that to the Git endpoint in the typical https://un:pw@bitbucket.org/path/to/repo format without issue.

  5. Kaleb Elwert

    We do return additional information when you are over the plan limit. It sounds like updating to a newer git client causes that to be displayed, so I'm closing this for now.

  6. Log in to comment