Troubleshooting Bitbucket repository errors

This guide lists and explains some common error messages that you may encounter when connecting a Bitbucket repository to your project. Where applicable, it also explains how to resolve the underlying issue. After following the steps to resolve an issue, if the error persists, raise a Support ticket. For more information about Support tickets, read Getting support. If you encounter an error that you think we should add to this guide, contact our Support team to let us know.

If your Git provider uses an IP allowlist, make sure the Maia IP addresses for Git repositories for your region are on it. Read Requests blocked by an IP allowlist for more information.

Desired repository not visible

Possible cause 1: Your user does not have sufficient permissions to view the Bitbucket repository

Solution: Have one of the admins of your organization check that the user account that you log in to Bitbucket with is a member of the intended Bitbucket workspace, and either the user or the relevant group to which they belong grants them write access to the repository.

Possible cause 2: Your organization has a large number of repositories

Explanation: Currently, Maia is configured to retrieve a maximum of 500 repositories from Bitbucket. There will be improvements to both search and pagination when fetching repositories coming soon; but unfortunately, there is not currently a workaround at this time. We are closely monitoring this limit, and will adjust accordingly.

Possible cause 3: You authorized with a different user that doesn’t have access to the desired repository

Solution: Follow the instructions in Reconnecting your Git user account with the user that has access to the desired repository.

Authorization fails

Possible cause: Maia can’t reach Bitbucket

Solution: If you receive an authorization error and you’re not using Bitbucket Data Center, refresh the page and try again. If the issue persists, either Bitbucket or Maia may be experiencing an issue.

Requests blocked by an IP allowlist

If your Bitbucket workspace restricts access to certain IP addresses and its IP allowlist doesn’t include the Maia IP addresses, Bitbucket blocks Maia. Maia then can’t list your repositories, connect a repository, or perform Git actions that interact with the remote repository, such as Pull remote changes. To resolve this issue, ask a workspace administrator to add the Maia IP addresses for Git repositories for your region to the workspace’s IP allowlist. For more information, read Control access to private content in a workspace in the Atlassian documentation.