Execute the file ServerSSHTroubleshoot.bat or sh from the <AppManager_home>\bin\troubleshooting folder (<AppManager_home>\bin in older versions of Applications Manager).
Via command Prompt Execute the ServerSSHTroubleshoot.bat or sh file. It will prompt for the details to connect (some prints will come between this prompts which you can ignore)
Below is a working example for the server with IP 192.168.1.10 and key /root/.ssh/id_rsa (user entries are in bold, comments in italic)
C:\Program Files (x86)\ManageEngine\AppManager11\bin\troubleshooting>ServerSSHTroubleshoot.bat -connection key
(use 'password' instead of 'key' if password is used for authentication, Eg : ServerSSHTroubleshoot.bat -connection password)
Default port -> hostname (example 192.168.1.10)
User-defined port-> hostname:port (example 192.168.1.10:8844)
Do you want to allow this host key? [Yes|No|Always]: Yes
(enter yes here)
(enter remote host's username)
Path to private key file?/root/.ssh/id_rsa
(you can copy the ssh private key and paste it a text file in AppManager server, give that file's local path here. Example: C:\sshprivatekey.txt )
If you are using password based authentication the syntax is as follows:
C:\Program Files (x86)\ManageEngine\AppManager11\bin\troubleshooting>ServerSSHTroubleshoot.bat -connection password
You will be prompted to enter the password instead of the path to the private key file.
Wait till the file executes completely and returns to the command prompt.
Now, copy the entire command prompt screen to a text file and send it to us (right click on the top of the command prompt Window->edit->select all). We will update you based on our analysis of the above information.