AIO Plugin unable to push code to RDE environment or use any commands | Community
Skip to main content
V
vashishth47
Level 2
September 18, 2025
Solved

AIO Plugin unable to push code to RDE environment or use any commands

  • September 18, 2025
  • 1 reply
  • 1198 views

I'm unable to push code or use any commands like aio aem:rde:status.

 

I've used the following command also to disable SSL checking and still the error is being thrown.

Used the 

export NODE_TLS_REJECT_UNAUTHORIZED=0 

npm config set strict-ssl false   

commands also, I have selected my org but through aio aem:rde:setup command and it was showing as setup complete. Please find the screenshots attached for reference.

Best answer by giuseppebaglio

hi @vashishth47,

commands like export NODE_TLS_REJECT_UNAUTHORIZED=0 and npm config set strict-ssl false only influence client-side certificate validation and do not affect issues where the negotiated TLS version is unsupported or when the server expects a higher protocol version than your client is using.

The error seems to suggest that your Node.js or system’s OpenSSL library does not support the TLS version required by Adobe’s endpoints:

  • Ensure your Node.js is recent (at least v18.x or v20.x)

  • Update your system’s OpenSSL to a recent version that supports TLS 1.2 or TLS 1.3

Another issue could be related to corporate networks or VPNs, which sometimes intercept SSL traffic and downgrade or block certain TLS versions:

  • Test by connecting from another network (e.g., mobile hotspot)
  • Temporarily disable VPN/proxy and retry.

1 reply

giuseppebaglio
giuseppebaglioAccepted solution
Level 10
September 18, 2025

hi @vashishth47,

commands like export NODE_TLS_REJECT_UNAUTHORIZED=0 and npm config set strict-ssl false only influence client-side certificate validation and do not affect issues where the negotiated TLS version is unsupported or when the server expects a higher protocol version than your client is using.

The error seems to suggest that your Node.js or system’s OpenSSL library does not support the TLS version required by Adobe’s endpoints:

  • Ensure your Node.js is recent (at least v18.x or v20.x)

  • Update your system’s OpenSSL to a recent version that supports TLS 1.2 or TLS 1.3

Another issue could be related to corporate networks or VPNs, which sometimes intercept SSL traffic and downgrade or block certain TLS versions:

  • Test by connecting from another network (e.g., mobile hotspot)
  • Temporarily disable VPN/proxy and retry.
    V
    vashishth47Author
    Level 2
    September 18, 2025

    Hi @giuseppebaglio ,

    The issue was related to the VPN only. It worked after using the mobile hotspot and disabling the VPN together.

    Terms & ConditionsAccessibility statement

    Loading footer...