SSH connection refused.

Dev Community Apps & Creations
1

Hi,

I am trying to use SSH on pi 2 rasplex 0.5.1 but get connection refused, I have tried with  winscp and putty  with same results.

 

winscp did make the connection once but locked up while I was transferring a skin to the pi, since then I always get connection refused.

 

I have tried turning SSH  on/off multiple times in  the rasplex gui,I burnt a new image multiple times, have burnt to another sd card all with  the same results.

I have also added SSH to cmdline.txt but still no good.

 

What else can I try ?

 

2

Hi,
I am trying to use SSH on pi 2 rasplex 0.5.1 but get connection refused, I have tried with  winscp and putty  with same results.
 
winscp did make the connection once but locked up while I was transferring a skin to the pi, since then I always get connection refused.
 
I have tried turning SSH  on/off multiple times in  the rasplex gui,I burnt a new image multiple times, have burnt to another sd card all with  the same results.
I have also added SSH to cmdline.txt but still no good.
 
What else can I try ?

I recently had a similar problem connecting to the SSH server in the latest RasPlex version, but after some experiments and discussion with other users the problem turned out to be due to obsolete SSH client coding.

I had tried using PuTTY and the SSH client built into UltraEdit, and both failed.
But my PuTTY version was 0.55, and when I upgraded it to 0.63 that one worked fine.
Apparently SSH connection negotiation has been modified over the years, in ways that require client changes.

I now have no connection problems using PuTTY 0.63, though the SSH client in UltraEdit still fails to do it right.

Best regards: dlanor
3

Hi,

I checked my PuTTY and it is 0.63, other than adding my rasplex ip address and port 22 do I need to configure anything else in PuTTY ?

Edit: I have found the problem, somehow I ended up with  another device with the same IP address as rp2 rasplex on my network.

4

I had the same problem, using PuTTY version .64. I was able to fix it by going into the System settings and resetting rasplex back to its initial defaults. Of course, I had to configure all my settings after the reset, but I was about to do a full reinstall anyway. If you have a complex setup, you might want to try saving your configuration (another menu option in the System settings) before resetting back to defaults. You can restore your configuration after the reset. (I didn’t try this… it’s possible the SSH bug is somehow related to your configuration, and might come back when you restored your saved settings. If so, just reset back to defaults again.)