GitLab拉取远程仓库镜像功能失效求助（BitBucket源）

Yep, plenty of gitlab.com users have hit this exact snag when trying to mirror BitBucket repos via the built-in pull mirroring tool. Let’s break down the most common issues and fixes that usually resolve this:

• Double-check your BitBucket authentication
  BitBucket no longer allows using your regular account password for HTTPS API access—you need an app password instead. Head to your BitBucket account settings, create an app password with at least Repository Read permissions, and make sure you’re using that (plus your BitBucket username, not email) in GitLab’s mirror config. Typos or wrong permissions here are the #1 cause of failures.

• Verify the remote repo URL
  Ensure the URL you entered in GitLab matches the exact HTTPS clone URL from BitBucket. It should look like https://<your-bitbucket-username>@bitbucket.org/<workspace-name>/<repo-name>.git. Missing the workspace name or using an SSH URL by accident will break the sync.

• Check GitLab’s mirror logs for specific errors
  Don’t guess why it’s failing—look at the logs! Go to your GitLab repo’s Settings > Repository > Mirroring repositories, then click the "Logs" button next to your mirror entry. The error message here will tell you exactly what’s wrong (e.g., "permission denied", "merge conflict", or "invalid credentials").

• Rule out GitLab repo restrictions
  If your GitLab repo has protected branches, mandatory CI/CD pipelines, or repository rules that block pushes, the mirror sync might fail when trying to update. Temporarily disable these restrictions to test if they’re blocking the sync.

• IP whitelisting (if your BitBucket workspace uses it)
  If your BitBucket workspace restricts access to specific IPs, you’ll need to add GitLab’s cloud IP ranges to the whitelist. GitLab publishes these ranges for their cloud users—you can find them in their official docs.

• Reset the mirror configuration
  Sometimes the mirror’s local state gets corrupted. Delete the existing mirror setup, wait 5-10 minutes, then re-configure it from scratch. This clears any stale cache that might be causing the failure.

If none of these work, you can also try a manual sync via the command line to test the connection:

git clone --mirror https://<bitbucket-username>:<app-password>@bitbucket.org/<workspace>/<repo>.git
cd <repo>.git
git push --mirror https://<gitlab-username>:<gitlab-access-token>@gitlab.com/<gitlab-namespace>/<repo>.git

If this command fails, the error will give you a clear clue about what’s broken.

内容的提问来源于stack exchange，提问作者Victor Cataraga