GITLAB_4
Issue
Glean was unable to fetch the members of one or more GitLab projects using the access token that was provided. Glean reads project members to enforce permissions, so the crawl cannot proceed until this check passes.
Resolution
- Confirm the personal access token is valid and not expired, and that it has the read scopes used during setup (
read_user,read_api,read_repository). - Confirm the token's user can access the projects in scope. The
/membersAPI only returns members for projects the token is allowed to see. - Confirm the Glean crawler can reach your GitLab Server instance. Self-hosted instances often require IP whitelisting so the crawler can call the API.
After updating the configuration on the GitLab Server data source setup page, save to re-validate.
If the problem persists, contact Glean Support.