Applications Manager Plugin not accessible after enabling SSL in OpManager
If Applications Manager Plugin is not at all accessible using HTTPS port
- We have automated the steps to refer to OpManager's Keystore when SSL is enabled in OpManager.
- Make sure that Applications Manager's server.xml file under <Applications Manager Home>\working\apache\tomcat\conf directory has keystorePath value as the absolute file path of OpManager's keystore.
- If connector tag specific to SSL Configuration in server.xml file has keystoreType key, verify its value. (i.e.) the File type given in the keystorePath should belong to the value of the keystoreType.
If the customer needs to use his own Keystore. Follow the below steps:
Connect to the Applications Manager's database and execute the below query:
UPDATE AM_GLOBALCONFIG SET VALUE = 'true' WHERE NAME = 'Plugin_CustomiseSSLConfiguration';
Using your own Keystore:
* Paste your Keystore file's absolute path as value for keystorePath in Applications Manager's server.xml under <Applications Manager Home>\working\apache\tomcat\conf\backup directory.
* Enter your keystore password as value for keystorePass
under <Applications Manager Home>\working\apache\tomcat\conf\backup
directoryImporting certificate to Applications Manager Plugin's default Keystore
KB to import your own certificate to Applications Manager Plugin's keystore. Note:
Make sure to update Keystore path and password in AppManager_Home\working\apache\tomcat\conf\server.xml with default keystore values i.e. Path and password of AppManager_Home\working\apache\tomcat\appmanager.keystore
NOTE: If encryptedKeystorePass key is already present there, update the key name with keystorePass.
If Applications Manager Plugin is accessible via HTTPS protocol but UI not loaded inside OpManager
Customers might be using a self-signed certificate or an untrusted domain certificate. Hence, try accessing Applications Manager with HTTPS using the Hostname from AMServer.properties file (located under <Applications Manager Home>\conf directory), in a separate tab in the same browser where OpManager is logged in.
Accept the risk warning page and proceed.
Now logout OpManager, log in again and check the APPS tab.
Troubleshooting SSL Handshake Error
SSL Handshake Error SSL Handshake error occurs when a secure connection cannot be established to the URL added for monitoring. Common reasons for it are wrong SSL protocol version, incompatible ciphers, and invalid/missing client-side certificate. ...
Alert from Applications Manager Plugin is not escalated to OpManager
Note: Only health attribute's alert from monitors will be escalated to OpManager Prerequisite: Below options should have been enabled Admin -> Action / Alarm settings -> “Enable Alarm notifications to OpManager Server” Check the hostname/IP ...
Troubleshooting Applications Manager Plugin (APM Plugin) issues in OpManager/OpManager Plus
Browse through the following topics to troubleshoot the actual problems encountered in Applications Manager Plugin (APM Plugin) for OpManager and resolve them accordingly: APM Plugin is down abnormally If the APM plugin is installed as a service, ...
LDAP - Unable to find valid SSL Certificate
If there is an error while adding LDAP Server Monitor with the message "Unable to find valid SSL Certificate", then please try the below steps to troubleshoot the issue. When the error occurs we can find the below traces in the "stderr.txt.*" log ...
How to monitor SSL Certificate of FTPS server?
Two modes to invoke client security in FTPS Explicit mode Implicit mode Explicit mode (Default port 21) - This port shouldn't be used In Explicit mode, an FTPS client must "explicitly request" security from an FTPS server by sending an FTP command ...