Important: Please read the Qt Code of Conduct - https://forum.qt.io/topic/113070/qt-code-of-conduct

SSH connection failure between Qt Creator and Linux Device



  • Hello,

    I'm trying to connect Qt Creator with a Beaglebone Black, but when I test connection between host and target I get an error message that says SSH connection failure.

    My host is a PC with Ubuntu 14.04 and Qt Creator 3.0.0.
    My target is a Beaglebone Black with Debian 9.5.

    The connection between QtCreator and the target is set to use a password. The connection via terminal between host and target is ok (ssh root@192.168.7.2).

    The first time that I try to communicate host and target I get the following message:
    Qt no comunica 1.JPG

    If I close Qt Creator and open it again then I get the following message:
    Qt no comunica 2.JPG

    However, communication between the host and a Beaglebone Black with Angstrom works perfectly.

    Could someone help me solve this problem?. Thanks.


  • Lifetime Qt Champion

    Hi,

    You should check the version of OpenSSH on your device. There might be a configuration issue with regards to the protocols available on your target and the one authorized on your host.



  • Hello SGaist,

    Version of OpenSSH on host => OpenSSH_7.4p1, OpenSSL 1.0.1f 6 Jan 2014
    Version of OpenSSH on target => OpenSSH_7.4p1 Debian-10+deb9u7, OpenSSL 1.0.2l 25 May 2017

    Thanks.


  • Lifetime Qt Champion

    Hi @maher_electronic,

    are you really limited to such old program versions?

    • Ubuntu 14.04 is no longer supported, 20.04 is just around the corner
    • Creator 3.0.0 is also quite old, we have seen 16 major releases since then

    Regards



  • Hello aha_1980 ,

    I'm using old versions because I compiled Qt 4.8.5 libreries for Beaglebone Black with Angstrom 5 years ago and I have continued using these versions.

    Now I have decided to try a newer operating system for Beaglebone Black because I want to solve a problem that I have detected in my project.

    Thanks.


Log in to reply