DocumentationExperience Cloud KCS

OSGi Console access fails in Adobe Experience Manager as a Cloud Service

Last update: October 22, 2026

In Adobe Experience Manager as a Cloud Service, attempts to access the OSGi Console at /system/console fail. Direct access to /system/console is disabled by design to ensure platform security and consistency. To fix this issue, use supported configuration and monitoring methods in Adobe Experience Manager as a Cloud Service.

Description description

Environment

Adobe Experience Manager as a Cloud Service (all environments)

Symptoms

Attempts to access the OSGi Console at /system/console in any environment fail. The page might not load, might return an error, or might not allow authentication. As a result, users are unable to review or modify OSGi configurations or monitor bundle states through the Felix Web Console.

Cause

Direct access to /system/console is disabled by design in AEM as a Cloud Service to ensure platform security and consistency. Supported configuration and monitoring operations are provided through the Developer Console and Cloud Manager deployment processes.

Resolution resolution

Follow the steps below to resolve the issue.

  1. Use the Developer Console to review OSGi configurations and bundle/component states:

    1. Log in to Adobe Cloud Manager with the required permissions.
    2. Navigate to Environments and select your environment’s Author instance.
    3. Click on “Developer Console”.
    4. In the Developer Console, use the “Status Dumps” or “Configurations” section to review active OSGi configuration PIDs and their resolved values.
    5. Review the “Bundles” and “Components” sections for their current state and activation status.

  2. To modify OSGi configurations:

    1. Make configuration changes in your AEM project codebase (for example, in .cfg.json files).

    2. Use the supported syntax for referencing environment variables, such as:

      1. some.property = $[ env:VARIABLE_NAME]
      2. some.secret = $[ secret:SECRET_NAME]
      3. Deploy the updated code through the Cloud Manager pipeline.

  3. After deployment, use the Developer Console to verify that the new configurations are active and resolved as expected.

recommendation-more-help
experience-cloud-kcs-help-kbarticles