IBM Support

QRadar: Troubleshooting SSH when connections cannot be established



If you cannot SSH from the Console, it might be the result that SSH keys are corrupted or have permission issues. This article talks about how to diagnose and resolve these types of issues.

Resolving The Problem

If you cannot SSH from the Console, the examples below will provide Administrators an overview of what can prevent a tunneled connection in QRadar with potential workarounds.

Managed Tunnel Key directory (Console only)

If connections are being created properly between appliances, the Console should have one key for each encrypted host. Administrators can review their system to determine that each host has a key and that the ownership is as defined in the example.

[root@Console-1 ~]# ls -al /store/configservices/staging/globalconfig/ssh_public_keys/
drwxr-xr-x 2 nobody nobody 62 May 2 20:19 .
rwxrwxr-x 9 nobody nobody 24576 May 3 10:10 ..
-rw-r--r-- 1 nobody nobody 406 May 2 18:25 Console_key
-rw-r--r-- 1 nobody nobody 409 May 2 18:27 host_103_key
rw-r--r-- 1 nobody nobody 409 May 2 20:19 host_104_key

Review the permissions within the /root/.ssh directory (Console & managed hosts)

Permissions on the .ssh directory should be 700 and the files within the directory should be 600. For Console appliances and managed hosts, the files to review are in the /root/.ssh directory. Administrators check and fix permissions on directory /root/.ssh/ and SSH files.
[root@Console-1 .ssh]# ls -la .ssh/
total 24
drwx------ 2 root root 4096 May 2 18:35 .
dr-xr-x---. 4 root root 4096 May 2 18:38 ..
-rw------- 1 root nobody 426 May 2 18:35 authorized_keys
-rw------- 1 root nobody 1675 May 2 18:25 id_rsa
-rw------- 1 root nobody 406 May 2 18:25
-rw------- 1 root root 788 May 2 18:25 known_hosts

If permissions are incorrect, then Administrators should update permissions as instructed below:
[root@Console-1~]# chmod 700 /root/.ssh
[root@Console-1~]# chmod 600 /root/.ssh/*

Review the Console's public key file is present on the managed host

If the Console's is not in remote host's /root/.ssh/authorized_keys or there are no local public/private keys, then the SSH session will request a password. This password request due to a missing authorized key can prevent the tunnel from being created properly.
[root@Console-1 ~]# ssh
- SSH public key login from managed hosts to the Console is no longer automatic.
- SSH public key login from a QFlow to a Flow Processor is still automatic.

  1. Log in to the Console using an SSH session as root user.
  2. Copy the keys using the command: ssh-copy-id user@host
    Example of command and output
      #ssh-copy-id root@
        /usr/bin/ssh-copy-id: INFO: Source of key(s) to be installed: "/root/.ssh/"
        /usr/bin/ssh-copy-id: INFO: attempting to log in with the new key(s), to filter out any that are
        already installed
        /usr/bin/ssh-copy-id: INFO: 1 key(s) remain to be installed -- if you are prompted now it is to  
         install the new key
         root@'s password:
        Number of key(s) added: 1
        Now try logging into the machine, with:  "ssh 'root@'" and check to make sure  
        that only the key(s) you wanted were added.

Remote hosts SSH public key is wrong in local hosts /root/.ssh/known_hosts.

If the public key is incorrect on a host, this could be the cause of why an SSH connection cannot be established. When a standard SSH session cannot be established, then attempting to add a managed host with a tunnel would also fail to be added properly. The information below outlines how to review known SSH hosts issues.

In the example below, attempting to open a standard SSH session from the Console to a managed host cannot complete due to key not being found in the known_hosts list.

[root@QRadar-3100 .ssh]# ssh

The error message 'Offending key in /root/.ssh/known_hosts: 2' indicates to the Administrator that line #2 in the known_hosts file is incorrect. Administrators can either compare the fingerprint.
The error message looks similar to:
Last login: Tue May 3 16:32:30 2016 from
This server was upgraded to QRadar on Thu Apr 7 16:05:15 EDT 2016
with patch applied on Mon Apr 11 14:00:17 EDT 2016

[root@Qradar726-1201 ~]# ssh
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
Please contact your system administrator.
Add correct host key in /root/.ssh/known_hosts to get rid of this message.
Offending key in /root/.ssh/known_hosts:2
RSA host key for has changed and you have requested strict checking.
Host key verification failed.

Administrators can use the command below to correct or remove line #2. After line #2 is removed or corrected, Administrators can attempt to connect by using SSH to get a prompt to update the known_hosts list or if the key was corrected, then the SSH session would be established without any prompts to the user. 
  1. Log in to the QRadar Console using an SSH session.
  2. If the error message is not originating on the console SSH to the offending managed host.
  3. At the prompt type:
    ssh-keygen -R <IP of host>
    ssh-keygen -R 
    Example where line 2 responds to
    ssh-keygen -R

Document Location


[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSBQAC","label":"IBM Security QRadar SIEM"},"Component":"Deploy","Platform":[{"code":"PF016","label":"Linux"}],"Version":"All Versions","Edition":"","Line of Business":{"code":"LOB24","label":"Security Software"}}]

Document Information

Modified date:
18 November 2021