Problem | Customers are unable to download adrum js files from CDN location(cdn.appdynamics.com). The error message for each customer may differ. For example, some common errors seen are: When you try to click the download option, it says No jsagent file can be downloaded from cdn.appdynamics.com. When you click on the download option, it just navigates and throws HTTP 400 or Error 404 When you click on the "Download" button, the page keeps on "waiting" for the server for a very long time, then redirects you to the Controller restAPI download token. It will look something like this:  http://controllerhost:8090/controller/restui/browserRUMConfig/downloadJSAgentZip?X-CSRF-TOKEN=4af3c63838922874d558da04b9dff079e07d1afb* It then immediately closes the connection with an "unexpectedly closed the connection" message.  Environment (AppD Version, Other Products Installed) affected: This issue is seen on 4.3.x and 4.4 Controllers. In this article Troubleshooting/Resolution    |   Quick Fixes   |   Disclaimers Troubleshooting/Resolution There can be multiple factors behind this download issue, so debug them step-by-step and apply the respective solutions as needed: NOTE | See the Disclaimers, below, to help inform your workaround choice Case 1: Is there an internet connection? Check whether there is an internet connection on the Controller machine. Many times the Controller machine does not have internet so it can't connect to cdn.appdynamics.com for downloading files.  Solution Case 1: If you can not get internet on the Controller machine, you can use one of the workarounds given in the Quick Fix of this article, below. Case 2: Is the firewall blocking connection on port 443? The firewall is blocking the connection to cdn.appdynamics.com on port 443. Solution Case 2: You need to open the firewall to connect to the CDN site in order to download the JSAgent files Case 3: Is there a proxy between the Controller and internet? There is a proxy in between. Solution Case 3: If the Controller server is connected to the internet via http/https proxy, verify the controller proxy settings are set up correctly. If not, your network team needs to set the proxy parameters to allow outgoing traffic to be bypassed. Back to top Quick Fixes While case-wise solutions are already provided in section above, here are some quick workarounds for immediate relief: Workaround 1: Get the latest JS Agent files All the latest js agent files can be downloaded from the following cdn locations:  1. adrum-latest.js - here 2. adrum-ext.js - here 3. adrum-xd.html - here    Workaround 2: Download the adrum folder onto a different machine Download the adrum files zip folder from the Controller on a different machine/laptop that has internet connection and use that. Workaround 3: Use the "...hosts all JavaScript Agent files..." option Download the files from your Controller using the "AppDynamics hosts all JavaScript Agent files from cdn.appdynamics.com" option. Steps 1-6 are below with screenshots attached for clarity: 1. Choose "AppDynamics hosts all JavaScript Agent files from cdn.appdynamics.com" Step1 2. Click on option 3. Save config and generate HTML snippet. Step2  3. Search for "scr" variable in the generated snippet. That will be the URL of your version specific adrum.js file. step3 4. Get adrum.js file: Open the URL copied at step 3 in a browser and save/download the resultant file as adrum.js. Step4 5. Get adrum-ext.js file: In your adrum.js file downloaded at step 4, search for "ext" and pick up the cdn URL for adrum-ext file. Open the URL copied above in a browser and save/download the resultant file as adrum-ext.js. step5 6. Get adrum-xd.html: In your adrum.js file downloaded at step 4, search for "html" and pick up the cdn URL for adrum-xd file. Open the URL copied above in a browser and save/download the resultant file as adrum.js step6 Back to top Disclaimers If you are using a SaaS Controller, you can download the latest version of files as mostly it will be on same major version. If you have an On-Prem Controller or your version is not on the same major version as EUM SaaS, you need to download the files specific to your version, which can be done via the browser following workaround #3 given in the Quick Fix section. ... View more

Issue  What should I do if my EUM Server is unable to start because of below error? Error Starting EUM Processor Server  |      com.google.inject. CreationException: Unable to create injector, see the following errors: Error in custom provider, com.singularity.ee.util. security.credentialstore. exception. CryptoOperationFailureExceptio n: Failed to decrypt: Illegal key size or default parameters Error in custom provider, com.singularity.ee.util.security.credentialstore.exception.CryptoOperationFailureException:  Failed to decrypt: Input length must be multiple of 16 when decrypting with padded cipher..... Cause And Solution This error is mostly seen post-upgrade or during upgrades, which stops the EUM upgrade/startup or login process.   This usually happens when encrypted/obfuscated values in the  eum.properties  are incorrect. In order to fix this, edit your eum.properties file with the properties below and restart your EUM server   1. Change  onprem. useEncryptedCredentials=true to false -->   onprem. useEncryptedCredentials=false   2. Set the password in plaintext for the below properties: onprem.dbPassword=<<plaintext passowrd>> onprem.credentialKey=<<plaintext passowrd>>   3. If the upgrade was from 4.0 to 4.5, you might also have to update the password in   <eum_server_home>/ eum-processor/bin/liquidbase. properties  for the  password  property.    4. Restart the EUM server.   If, however, you cannot use the plaintext passwords and you need to use encrypted passwords, you will need to regenerate the encrypted key for the the database password and obfuscated keys for the credential key. Then, update the eum.properties file and restart the EUM Server.  The database password may not be decipherable using the key in use. You can follow the steps below to complete this for this process: 1. Generate a new credential store: bin/eum-credential-key.sh generate_ks -storepass <store_password>   2. Generate a new obfuscated password for the credential store: bin/eum-credential-key.sh obfuscate -plaintext <store_password>   3. Generate a new database password: bin/eum-credential-key.sh encrypt -storepass <store_password> -plaintext <DB_password>   4 After this, modify the eum.properties file as: onprem.dbPassword=<<output of 3 above>> onprem.credentialKey=<<output of 2 above>> onprem. useEncryptedCredentials=true   5. Restart the EUM Server.    For additional information on this change the credential keystore password for the EUM Database click here.  ... View more