DocumentationExperience Cloud KCS

Resolve HTTP 403 errors when pushing to Cloud Manager Git repositories

Last update: September 8, 2026

This article explains how to resolve HTTP 403 permission denied errors that occur when pushing code to Adobe Cloud Manager Git repositories, typically caused by missing write permissions.

Description description

Environment

  • Adobe Experience Manager (AEM) Cloud Manager (all versions)

Issue/Symptoms

  • Unable to push code changes to any Adobe Cloud Manager Git repository.
  • Receiving an HTTP 403 error that indicates permission denied.
  • The issue persists after regenerating Git credentials and clearing cached credentials.
  • The error occurs across multiple repositories.

Example error messages:

  • error: RPC failed; HTTP 403 curl 22 The requested URL returned error: 403
  • send-pack: unexpected disconnect while reading sideband packet
  • fatal: the remote end hung up unexpectedly

The user has the Deployment Manager role assigned but still cannot push code. The Access Repo Info > Generate Password option is visible, and credentials have been regenerated.

Cause

The HTTP 403 error occurs when the required Developer or Deployment Manager role is not assigned in the Adobe Admin Console, preventing write access to Cloud Manager Git repositories.

Resolution resolution

Follow the steps below to resolve the issue:

  1. Confirm that you have either the Developer or Deployment Manager role assigned for the relevant Cloud Manager program in the Adobe Admin Console.
  2. If you do not have the required role, request your System Administrator to assign it. Only a System Administrator in your organization can assign these roles. Adobe Support cannot grant repository write access directly.
  3. In Cloud Manager, navigate to Access Repo Info > Generate Password to create a new Git credential. This will invalidate any previous credentials.
  4. If the Generate Password option is not visible, the required role is missing.
  5. Remove any locally cached credentials for git.cloudmanager.adobe.com from your credential manager or keychain.
  6. Run the following command to verify access:
git ls-remote    https://git.cloudmanager.adobe.com/<tenant>/<repository>/
  1. If the command succeeds, proceed to push code changes.
  2. If the issue persists, request your System Administrator to review your product profile and ensure the correct role is assigned in the Adobe Admin Console.
recommendation-more-help
experience-cloud-kcs-help-kbarticles