Unable to Verify SSH Details

Last updated on Sep 16, 2025
Applies To Sources and Destinations connecting through SSH with Hevo’s RSA-generated public key.
Error Message Text(s) - Unable to verify SSH details.
- Unable to connect. Please verify your SSH details and try again.

Error Summary

  • Hevo is not able to verify the credentials for connecting to the SSH server.

Potential Causes

  • The provided SSH server host details may be incorrect.

  • The Hevo IP addresses for your region are not whitelisted on the SSH server.

  • If the SSH server host is unreachable, the SSH connection fails.

  • Any extra space or line break in the public key can cause the SSH server to reject it.

  • The SSH server is hosted on a system with a newer operating system (OS) version, such as Ubuntu 22 or Amazon Linux 2023 (AL2023). On these systems, support for RSA-generated keys may not be enabled by default. The authorization log file /var/log/auth.log on your SSH server may display the following error when you try to connect: _userauth_pubkey: key type ssh-rsa not in PubkeyAcceptedAlgorithms.

Suggested Action(s)

  • Ensure that the SSH IP or hostname is correct and publicly reachable. To verify this, run the following command:

    ping <ssh-ip>
    
  • Before connecting through SSH, ensure that the Hevo IP addresses for your region are whitelisted on the SSH server.

  • Confirm that the SSH server is running and listening on the specified SSH Port. To verify this, run the following command:

    telnet <ssh-ip> <ssh-port>
    
  • Remove any line breaks or trailing spaces from the copied public key.

  • Use the Hevo ECDSA public key. For this, add the ECDSA key to the authorized_keys file on your SSH server host.

  • Enable support for RSA-generated public keys on your SSH server host. To do this:

    • On Debian Architecture-based Systems such as Ubuntu 22.04 LTS:

      1. Log in to your SSH server host.

      2. Access the SSH configuration file, sshd_config. This file is generally found in the /etc/ssh directory. Add the following lines to it:

        HostKeyAlgorithms +ssh-rsa
        PubkeyAcceptedKeyTypes +ssh-rsa
        
      3. Restart your SSH server using the following command:

        sudo systemctl restart sshd
        
    • On Red Hat Enterprise Linux-based systems such as Amazon Linux 2023 and CentOS 9:

      1. Log in to the AWS EC2 console and connect to your SSH server instance.

      2. In the terminal window, run the following commands:

        sudo dnf install crypto-policies-scripts 
        
        sudo update-crypto-policies --set LEGACY
        
      3. From the EC2 console, reboot your SSH server instance.


Revision History

Refer to the following table for the list of key updates made to this page:

Date Release Description of Change
Sep-16-2025 NA Added more potential causes and corresponding suggested actions.
Aug-16-2023 NA New document.

Tell us what went wrong