Bitbucket repository is read-only even though my Free workspace has only 1 user

Question

Hi Atlassian Community,

I’m having an issue pushing code to my Bitbucket Cloud repository through SourceTree.

When I try to push, I receive this error:

“Your push failed because the account 'sreevally' has exceeded its user limit and this repository is restricted to read-only access.”

The error returns HTTP 402.

I checked my workspace and found:

* Bitbucket plan: Free
* Active users: 1
* Repository: Repo 1
* Repository size: 726 B
* Git LFS: 0 B used
* Bill history: No invoices
* I am the workspace/organization administrator.

The repository is private and I have already verified the repository settings. There does not appear to be a user-limit, billing, or repository-size issue.

Could someone please help me determine why the repository is being restricted to read-only and how I can restore push/write access?

Thank you.

Thijs D. | Dortus · Answer

Hi @Rajampeta Sreevally , That 402 message has two documented causes: more than 5 users in a Free workspace, or a failed payment that downgraded the plan (see this KB article: https://support.atlassian.com/bitbucket-cloud/kb/fix-error-your-push-failed-because-the-account-has-exceeded-its-user-limit ). From what you checked, neither applies, so two more things to look at: * Make sure the workspace named in the error ("sreevally") is the one you checked. The first part of the repo URL (bitbucket.org//) is the workspace that gets counted. If you have more than one workspace, open Workspace settings > Plan details on that exact one. * If it really is a single-user Free workspace, others have hit this after Bitbucket's cleanup of free, unused workspaces flagged their workspace. In this similar thread an Atlassian support engineer reactivated the workspace and pushes worked again: https://community.atlassian.com/forums/Bitbucket-questions/Bitbucket-Cloud-quot-User-limit-exceeded-quot-error-on-Free/qaa-p/3240494 . Only Atlassian can do that, so raise a request via support.atlassian.com/contact (billing and licensing) with the full error text and the workspace name. One user also saw it clear up on its own after a while, so retry a push once before you open the request.