Connectivity issues in AEM Rapid Development Environment over internal network

Last update: Mon May 19 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

Using Adobe Experience Manager (AEM) as a Cloud Service results in connectivity issues when accessing the Rapid Development Environment (RDE) through VPN or internal networks. The aem:rde:status command often fails with a connection refusal error in these scenarios. This article explains how to configure your environment to use a web proxy to ensure consistent connectivity across all network configurations.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS) - Sites

Issue/Symptoms

Organizations using Adobe Experience Manager (AEM) as a Cloud Service face connectivity issue when accessing the Rapid Development Environment (RDE) through a VPN or internal network. The aem:rde:status command fails with a connection refusal error, displaying the message:

Error: [ RDECLI:INTERNAL_STATUS_ERROR] There was an unexpected error when running status command. Please, try again later and if the error persists, report it.

Error FetchError: request to <endpoint> failed, reason: connect ECONNREFUSED <IP>:443

This issue occurs when connected via VPN or internal LAN/Wi-Fi.

Resolution resolution

To resolve this issue and enable consistent connectivity to RDE across all network configurations, follow these steps:

Set up your system to route all CLI requests through the Zscaler proxy by configuring HTTP and HTTPS proxy settings:
1. Set environment variables for HTTP_PROXY and HTTPS_PROXY in your shell or command prompt:
  
  export HTTP_PROXY="http://<zscaler-proxy-address>:<port>"
  
  export HTTPS_PROXY="http://<zscaler-proxy-address>:<port>".
  
  On Windows, use set instead of export, or configure these variables via system settings.
2. Alternatively, configure these settings directly in Adobe IO CLI:
  
  aio config:set HTTP_PROXY <zscaler-proxy-address>
  
  aio config:set HTTPS_PROXY <zscaler-proxy-address>
Ensure that the Adobe IO CLI and AEM RDE plugins are correctly picking up these proxy settings.
Confirm whether direct outbound traffic to RDE endpoints is blocked on your VPN or internal network. If it is, ensure that routing through the corporate proxy is enforced for all outgoing traffic.

After applying these configurations, retry accessing RDE using the aem:rde:status command. This setup should allow seamless connectivity regardless of whether you are on VPN or an internal network.

recommendation-more-help

3d58f420-19b5-47a0-a122-5c9dab55ec7f