I have been trying for ages to connect to my Edison from the IoT XDK to no avail. I keep getting the error: Error on ssh connection: Error: All configured authentication methods failed.
I have followed all the required steps from the https://software.intel.com/en-us/getting-started-with-the-intel-xdk-iot-edition setup tutorial and I still get the same error. However,the surprising thing is that I am able to connect to the board via both the SSH terminal and Serial terminal in the XDK as shown
I am using the latest edison image 159.devkit. The Edison address is 192.168.1.125, got that from >>ip address | grep wlan0. I have also ran configure_edison --password to set up the password and the board is automatically detected in the XDK,so everything should be fine,but it isn't. Below are the screenshots of the process and the error.
I do not know what's wrong,this is really frustrating. Kindly assist.
That's an abnormal behavior, are you sure you are running the latest xdk-daemon/xdk version/Yocto image?
In case you don't have the xdk-daemon or you don't know which version you have installed, you can get the latest version with the following commands:
opkg install xdk-daemon
You can find which version of the Edson's image you are using wit the command configure_edsion --version. In case you need it, the latest image can be found in http://software.intel.com/en-us/iot/hardware/edison/downloads Intel® Edison Downloads.
Updating the xdk-daemon i get Package xdk-daemon (0.0.35-r0) installed in root is up to date. I am also using the latest edison image 159.devkit.
The error still persists.
It seems that the issue is generated on the PC, and it's probably due to XDK. In that case, I'd suggest you to uninstall the XDK and install it again. Did you install it using the integrated installer? If so, I'd suggest you to install the standalone version that you can find in: https://software.intel.com/en-us/iot/software/ide IoT - IDEs | Intel® Developer Zone.
In case the issue persists after installing the XDK again, I'd test it on another PC to see if the issue is the PC.
Unfortunately, I haven't. Really tried but was not able to find a solution.
I've resolved to instead uploading the node,js files to the board and running them directly from there with node scriptname.js