Troubleshooting GitLab repository errors

This guide lists and explains some common error messages that you may encounter when connecting a GitLab 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 GitLab project

Solution: Have one of the admins of your organization check that the user account that you log in to GitLab with is a member of the intended GitLab project, or has been assigned a role that provides the ability to view and/or contribute to that project.

Possible cause 2: The repository is still “uninitialized”

Solution: If the repository was recently created, double check that it was initialized with a file such as a README. If the repository is entirely empty, some Git providers do not report that it is a valid repository for use, so creating a README file in the repository by any means is usually enough. After doing so, it should then appear when establishing a connection to GitLab within Maia.

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

Explanation: Currently, Maia is configured to retrieve a maximum of 2000 repositories from GitLab. 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. However, we are closely monitoring this limit, and will adjust accordingly.

Possible cause 4: 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 GitLab

Solution: If you receive an authorization error and you are not using a self-managed instance of GitLab, refresh the page and try again. If the issue persists, either GitLab or Maia may be experiencing an issue.

Requests blocked by an IP allowlist

If your top-level GitLab group restricts access by IP address and its IP allowlist doesn’t include the Maia IP addresses, GitLab 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 an owner of the top-level group to add the Maia IP addresses for Git repositories for your region to the group’s IP allowlist. For more information, read Restrict group access by IP address in the GitLab documentation.