Surface better errors for mirroring when group IP restrictions are enabled

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

• Work on this issue
• Close this issue

Proposal

When group IP restrictions are enabled for groups, it's possible for users to get errors even if they have the proper access to the projects:

13:fetch remote: "remote: The project you were looking for could not be found or you don't have permission to view it.\nfatal: repository 'https://gitlab.com/path/to/project.git/' not found\n": exit status 128.

Because the Git request is coming from the GitLab webfleet, the IP address will fall outside of a customer's IP range and we'll see the following in Kibana:

Attempting to access IP restricted group

To solve the issue, we have to add the GitLab IP range to the group IP restriction to make it work.

A solution to this could be:

1. Note in our documentation that you need to add our webfleet range so that other features like mirroring can work as expected.
2. Surface an error when mirroring that shows that the IP address is not within range.
3. Explicitly tell the user that IP restrictions are enabled and double check them if they are mirroring from GitLab.