Resolving AEM Package Manager upload/access failures (permissions, network, URL, and runtime restrictions)
Package Manager uploads or installs can fail when packages do not appear, access is blocked, or installation returns an undefined message.
You might be unable to open Package Manager, upload a package, view uploaded packages, or complete an installation. In some cases, uploads appear to finish but the package does not appear in the list. In cloud environments, installation can also fail when the package contains immutable content that is not supported at runtime.
Common causes include missing permissions, incorrect URLs, network restrictions, browser interference, and packages that contain immutable paths in cloud environments. Confirm the access path, test permissions and browser behavior, and review package filters for unsupported content. Use runtime package installation only for mutable content and deploy immutable content through the deployment pipeline.
Description description
Environment:
- Adobe Experience Manager as a Cloud Service
- AEM Managed Services
- Adobe Experience Manager on-premise
Issue/Symptoms:
- If Package Manager cannot be accessed at
/crx/packmgr, open the correct Package Manager URL for the target environment and confirm that/crx/packmgr/index.jsploads without redirect or access errors. - If no packages are visible in Package Manager, check whether another user with the expected access can view or upload packages to determine whether the issue is related to permissions.
- If a package upload completes but the package does not appear in Package Manager, refresh the interface and retry with a small test package to confirm whether the upload is being accepted and displayed correctly.
- If an upload fails with no clear error, retry the same action from a different network to determine whether a firewall or proxy restriction is blocking the request before it reaches AEM.
- If the browser shows an undefined error during installation, repeat the action in an incognito session or a different supported browser to rule out extension, session, or browser-specific interference.
- If a cloud environment rejects the package because it contains unsupported runtime content, review the package filters and confirm that the package contains only mutable content intended for runtime installation and does not include immutable paths such as
/apps.
Root cause:
These failures are typically caused by missing permissions on package paths, an incorrect Package Manager URL, network or firewall restrictions, browser extensions or session behavior that interfere with requests, local security tools that block uploads, or package filters that include immutable paths such as /apps in cloud environments.
Resolution resolution
Try the following steps:
- Open the correct Package Manager URL for the target environment and confirm that
/crx/packmgr/index.jsploads without redirect or access errors. - Check that the affected user has permission to create, upload, view, and install packages by comparing the result with another user who is expected to have the same level of access.
- If Package Manager does not open or uploads do not start, retry the same action from a different network to determine whether a firewall or proxy restriction is blocking the request.
- If the upload or install fails in the browser, repeat the action in an incognito session or a different supported browser to rule out extension, session, or browser-specific interference.
- If the same upload fails in both the target environment and a local SDK, review local or organizational security controls because the request may be blocked before it reaches AEM.
- For cloud environments, review the package filters and confirm that the package contains only mutable content intended for runtime installation and does not include immutable paths such as
/apps. - If the package includes immutable content, deploy that content through the deployment pipeline instead of Package Manager.
- After making changes, upload a small test package, refresh Package Manager, and confirm that the package appears in the list and installs without new errors.
If the issue continues after these checks, submit a ticket to Adobe Support when uploads fail in multiple browsers, Package Manager is inaccessible for all users, another user with similar access can complete the action while the affected user cannot, or testing shows that the request does not reach AEM. Include screenshots, HAR files, browser console logs, the package name, and a summary of the troubleshooting results.