Unable to use AIO Plugin | Community
Skip to main content
NageshRaja
NageshRaja
January 30, 2025
Solved

Unable to use AIO Plugin

  • January 30, 2025
  • 4 replies
  • 2076 views

Hey guys,

 

Getting the below error when trying to use AIO plugin to push artifacts to RDE, tail logs etc. 

Any help or ideas around this?

 

admin-sys digital-adobe-aem % aio aem:rde:install all/target/brandX.all-1.0.0-SNAPSHOT.zip 
 ›   Warning: @adobe/aio-cli update available from 10.3.1 to 10.3.2.
        ›   Run npm install -g @adobe/aio-cli to update.
Running aem:rde:install on cm-p000000-e0000001 (AEM as cloud service - RDE - AEMCS-RDE)
? The last RDE command ran more than 24h ago, do you want to continue running the command on cm-p000000-e0000001? Yes
No --type provided, using content-package
        ›   Error: [RDECLI:INTERNAL_INSTALL_ERROR] There was an unexpected error when running install command. Please, try again later and if the error persists, report it. Error FetchError: request to 
 ›   https://dev-console-ns-team-aem-cm-prd-n141370.ethos13-prod-can2.dev.adobeaemcloud.com/api/rde/program/000000/environment/0000001/runtime/updates failed, reason: unable to get local issuer 
        ›   certificate
 ›       at ClientRequest.<anonymous> (/Users/admin-sys/.local/share/@adobe/aio-cli/node_modules/node-fetch/lib/index.js:1501:11)
        ›       at ClientRequest.emit (node:events:519:28)
 ›       at emitErrorEvent (node:_http_client:108:11)
 ›       at TLSSocket.socketErrorListener (node:_http_client:511:5)
 ›       at TLSSocket.emit (node:events:519:28)
 ›       at emitErrorNT (node:internal/streams/destroy:169:8)
 ›       at emitErrorCloseNT (node:internal/streams/destroy:128:3)
 ›       at process.processTicksAndRejections (node:internal/process/task_queues:82:21) {
 ›     type: 'system',
 ›     errno: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY',
 ›     code: 'UNABLE_TO_GET_ISSUER_CERT_LOCALLY'
 ›   }
 ›   Code: INTERNAL_INSTALL_ERROR
Best answer by Rohan_Garg

Hi @nageshraja,

 

I noticed you had earlier asked query about RDE deployment failed status. If you were able to deploy previously but not now then something has changed with respect to the Cloud Manager.

As @aanchal-sikka mentioned, reach out to your IT Team to understand any org level access changes which might have been made to the cloud manager. I have had prior issues but most of them revolved around the Cloud Manager URL being whitelisted by the client's VPN. Outside of the VPN the aio plugin would work but not when connected to VPN.

 

Hope this helps!

Rohan Garg

4 replies

aanchal-sikka
Community Advisor
aanchal-sikkaCommunity Advisor
Community Advisor
January 30, 2025

@nageshraja 

 

Please refer to the section "Unable to push to RDE instance" on https://techrevel.blog/2024/02/14/aem-rde/

 

If you encounter the “unable to load certificates openssl” error while using status/install commands, you can apply the following quick fixes:

  • Temporarily disable SSL certificate verification:
npm config set strict-ssl false

Alternatively, you can bypass certificate verification by setting an environment variable:

export NODE_TLS_REJECT_UNAUTHORIZED=0
SET NODE_TLS_REJECT_UNAUTHORIZED=0       //For Windows command line

Please note that both commands pose a security risk as they bypass certificate verification, so they should only be used temporarily.

Aanchal Sikka
    NageshRaja
    NageshRajaAuthor
    January 31, 2025

    thank you for this but what's the way to troubleshoot this for a more permanent fix?

    aanchal-sikka
    Community Advisor
    aanchal-sikkaCommunity Advisor
    Community Advisor
    January 31, 2025

    @nageshraja 

     

    Its due to the security restrictions set by your organization. You might not notice this issue on personal laptop.

     

    Permanent fix is to talk to your IT department, and set the Environment Variable on your system.

    Aanchal Sikka
      Shiv_Prakash_Patel
      Community Advisor
      Shiv_Prakash_PatelCommunity Advisor
      Community Advisor
      January 30, 2025

      Hi @nageshraja ,

      As you're encountering a certificate-related error while using the aio aem:rde:install command to deploy an artifact. There may be the issue with SSL/TLS certificate validation in your local environment

      1. Check if your AIO CLI version is outdated, update it to the latest version (npm install -g @adobe/aio-cli).
      2. If your system has missing or misconfigured SSL root certificates, try temporarily disabling SSL(export NODE_TLS_REJECT_UNAUTHORIZED=0).
      3. Your session might be expired re-run (aio auth:login).

      If the issue persists, you can also check out my blog for any missing setup in RDE or to set it up again - Adobe Cloud Manager RDEs: Accelerating Development 

      Regards,

      Shiv Prakash
        NageshRaja
        NageshRajaAuthor
        January 31, 2025

        thank you for the response but updating the aio-cli version didn't work and neither did logging in again

        Disabling SSL works but can't establish it as a norm in the team so need a more permanent fix for this!

        Rohan_Garg
        Community Advisor
        Rohan_GargCommunity AdvisorAccepted solution
        Community Advisor
        January 31, 2025

        Hi @nageshraja,

         

        I noticed you had earlier asked query about RDE deployment failed status. If you were able to deploy previously but not now then something has changed with respect to the Cloud Manager.

        As @aanchal-sikka mentioned, reach out to your IT Team to understand any org level access changes which might have been made to the cloud manager. I have had prior issues but most of them revolved around the Cloud Manager URL being whitelisted by the client's VPN. Outside of the VPN the aio plugin would work but not when connected to VPN.

         

        Hope this helps!

        Rohan Garg

          NageshRaja
          NageshRajaAuthor
          February 4, 2025

          yes previously it worked but then the client put up the author and publish cloud URLs behind their firewall so now they are accessible only via VPN! Turned off the VPN and the aio plugin worked again! Thanks!

          AmitVishwakarma
          Community Advisor
          AmitVishwakarmaCommunity Advisor
          Community Advisor
          February 1, 2025

          The issue is likely caused by SSL certificate validation in your environment. Here’s how to fix it:

          1. Ensure correct SSL certificates: Verify that your system has the proper root certificates installed.
          2. Contact IT: Ask your IT team to whitelist the Cloud Manager URL and ensure SSL access, especially if you're on a VPN.
          3. Set Environment Variable Temporarily: Bypass SSL verification with:
          export NODE_TLS_REJECT_UNAUTHORIZED=0 (Linux/macOS)
          SET NODE_TLS_REJECT_UNAUTHORIZED=0 (Windows) This is a temporary workaround, not ideal for production.
          Update AIO CLI: Ensure you're using the latest version (npm install -g @61380/aio-cli) and re-login.

            NageshRaja
            NageshRajaAuthor
            February 4, 2025

            Thank you for the reply @amitvishwakarma, we indeed are on VPN! Have asked the IT Team for SSL access while being on VPN but for now stepping out of the VPN works so we're sorted! Thanks!

              Terms & ConditionsAccessibility statement

              Loading footer...