ÃÛ¶¹ÊÓƵ

Documentation

Private GitLab repository setup fails in AEMaaCS Cloud Manager

Last update: Tue Jul 22 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

While configuring a private GitLab repository in a Cloud Manager pipeline within ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service (AEMaaCS) – Assets, an error appears indicating that the repository URL cannot be resolved. To resolve the issue, ensure the repository URL is correct, publicly accessible, or by allowlisting ÃÛ¶¹ÊÓƵ’s egress IPs for internal access.

Description description

Environment

ÃÛ¶¹ÊÓƵ Experience Manager as a Cloud Service (AEMaaCS) – Assets

Issue/Symptoms

  • AEMaaCS Cloud Manager displays the error: The provided repository URL could not be resolved.
  • HTTP Status Code 400 (Bad Request) appears during repository validation.
  • Repository URL fails to validate even when it is correctly formatted and accessible internally.

Cause

ÃÛ¶¹ÊÓƵ’s Cloud infrastructure is unable to access internally hosted GitLab repositories that are not exposed to the public internet.

Resolution resolution

To resolve the issue, follow these steps:

  1. Verify the repository URL is correctly formatted and publicly accessible from the internet.
  2. Allow access to internal repositories hosted on an internal GitLab server that is not exposed to the public internet by allowlisting ÃÛ¶¹ÊÓƵ’s standard egress IP addresses for your Azure region. Refer to Introduction to IP Allow Lists for the IP list.
  3. Generate a personal access token with the required scopes (for example, api, read_user) to authenticate repository access.
  4. Refer to ÃÛ¶¹ÊÓƵ’s official documentation on Configure Advanced Networking for AEM as a Cloud Service for additional configuration guidance.

Add private repositories in Cloud Manager in the AEM Cloud Manager documentation.

recommendation-more-help
3d58f420-19b5-47a0-a122-5c9dab55ec7f