As
of now we do not support usage of SSH2 keys generated with passphrase in
Applications Manager. However you can use a key generated without passphrase.
Use the steps below to generate and use SSH2 keys.
If
users generate keys with key passphrases then they will receive the following
error:
Authentication failed. Kindly verify the username and password provided.
Check whether the PasswordAuthentication is set as yes in /etc/ssh/sshd_config
file.Kindly set it as yes and restart the SSH daemon
Sample Key Format:
With Passphrase – WON’T WORK
-----BEGIN RSA PRIVATE KEY-----
Proc-Type: 4,ENCRYPTED
DEK-Info: DES-EDE3-CBC,288E9F707C47086E
9+SMwolsFe9UY7xXXGUpb+SgnyEYl0eAoBgEIJYIlWvUstIdN28Ai/lzqhZJUAp/
xLNDYk80RL5JLwzjH4iSQp2JM6UUithNX6byDOLCphcBfx/88eWt0NAv2Z8e82iM
oou3BFkj/1Jgdiq9aZLbc8EiWoN787OII8G/yU6lFOQCYryKwkV1uBIJZNV0PIvx
XtDw+XEi1l4Nk9wlAv1Amg2Hrsq5E5Q9bi5Cv1R/GmOhtkN+22d50ugo7q73fmGj
OJdpXD8dllvkyl3yH7AOWMm/cOxU5fDPmmg9JtZLdx/A1I2gfmDuUEe7wany9hS5
DnkFNBWe6XWfjpVN37bGZ4Ihh2RIg83nwz4+ivz3TRJZcNudku3LT3kbZbvSdex9
wAkrv3+YoRzF504Vcs37+5ldF4LO4nU6oSAylRGSHk8pRObjhnL4uWlNWNGWlirY
ZLhuptcfeGVAR8Cazg+W4ZLosawMTVt2dupVXzop4JSCL+1kC0FHuSJDbPY2SNr3
xkqMaMsuh8+mNQvBIUDIBxEQi1ZF5YFl70BejJMnqulV5XvT1W/VV2DJN96ZyA2a
hV//0ktO+ElyY/wF4HuSDKBGFiLgszJZ32jpV0xo1q5SQTOrUU57u0ML9KVLekq9
hzaP8icef40btoUEH6XZubHp2QqKDgeCMZMPNlHDcGaLXZeoNsCZ6OLnc2DBnT9R
Oe1do8ouU94CShEONAhA3dUgxjqNQWCxmY55ToOAJVudm711a85DDdiVifUGilOm
RSTZM5OTzuBCCotYBVwA8D1M610vzEGh3YeyWA005pQ=
-----END RSA PRIVATE KEY-----
Without Passphrase – WILL WORK
-----BEGIN RSA PRIVATE KEY-----
MIICXAIBAAKBgQDCTq9g0fgoCknPuLfZ19B8YtCN5zg6YIJA8zZWMEi2XtWY7AkF
GqGmzDj5+BoCJdcn07a1D6n4RfO+STujulbh4V/Aka6AudJ4Z12cBhZias4h5oxT
yVdCOYKO5dgXMnQOgcrLpH+z3SWlu4pL96gDP1dcRJG1pw4PvPlUwMJSMQIBJQKB
gQCdi+gk/UW/maOhgQPFYuBk2n+Vprf3+zktvke7gRhchD57/aZy11Ki6sZp0BUW
f4vbGlzKKGBMwxioH7PQ3EZwiky8rxPGMFfHnKzO0BQjlDt+Zit4yd1jwemhdIYy
GF2w/ofwj5aHOI3uLCUD1hWpD8o6QwMl3NqN7hzO/RicZQJBAPCNeNtOJyiXF8xr
q6VUM+j8O1vn+Si4QVdfXbKWIQA5NQMcCl0CQxVFsElu3WUlFs1Y/pJBXyTt76Z6
Z7XKUgsCQQDOyPiaLlyZ4C6vC74b3Iso3du3TJr8/OO3PsfwWC/g+n8zscNBEJbO
7KUIdlA9rHnNc+Kj7pa+igqkBg/j4i4zAkEAr4nUu7WSMmBrT/uLF8fS2nLfNTqT
OWPcp4rH1VjL+T6AoWd9Lx1TjBBCXxmMzUSUGU7HmyjI45jfT/h1MaF6IwJAEMQv
1SZaiQRWz+wyAkJQeO9k14LAdWCc14GhgjCp76WbnGhb8ITN9RobOAmXzaYzY69z
PblmKx/zBmFbO/2VCwJBAKjc3Decx2jtgAr0X94txc2uOkUjLUCp/RyraWDgVZUS
+Z6Sl4wAK4GB6+GADMwt7PEv4rcFO0KOjGJw4ZO9TkA=
-----END RSA PRIVATE KEY-----
If you still have issues send below information to
appmanager-support@manageengine.com for further troubleshooting
1) Send us complete output for the AppManagerHome\bin\ServerSSHTroubleshoot.bat
or ServerSSHTroubleshoot.sh script with remote server hostname or ipaddress.
2) Send us copy of /etc/ssh/sshd_config file (or /etc/sshd_config file) from
the remote server which are trying to add in Applications Manager via SSH
3) Open command prompt in remote server that you are trying to monitor in
Applications Manager with SSH
uname -a
/sbin/ifconfig -a
dladm show-link
hostname
4) Open command prompt in Applications Manager host and execute below command
with remote server hostname or ipaddress and send us the screenshot of the
output
telnet <hostname> <ssh_port>
Example:
telnet app-centos 22
5) Open command prompt in Applications Manager host and execute below commands
with remote server hostname and ipaddress and send us the screenshot of the
output
ping hostname
nslookup hostname
ping ipaddress
nslookup ipaddress
6) Try to add the server monitor in Applications Manager a couple of times and
then immediately create a new support information file and upload it to our
ftp.Refer the below link for steps to create support information file and
uploading it.
https://desk.zoho.com/portal/manageengine/kb/articles/where-do-i-find-the-log-files-that-i-need-to-send-to-technical-support-team-for-analysis
7) Check if you are able to connect with the same username & SSH KEY using
any other SSL client tool other than Applications Manager.