GPi SSH/PuTTY issues

tmshll

Hi all, extremely new to Retropie.

I've set up my Retroflag GPi case, following the guide on howchoo. Retropie is installed, buttons configured, WiFi enabled. So far so good.

Now I'm trying to use SSH to add the Safe shutdown script (and some ROMs) to my GPi. I've installed PuTTY on my laptop (Windows 10). Got the IP from Retropie, enabled SSH on the device. I try to connect using PuTTY and immediately get the following message:

Network error: Software caused connection abort.

I've looked around and seen that this message can occur with timeouts, but I'm seeing it as soon as I hit open connection.

I'm sure there's a fix here and I've probably missed something obvious, but any help would be appreciated :)

celly

@tmshll are you using the official retropie image or a premade build for the GPi Case?

tmshll

@celly Hi, I used the Retropie image for 0/1 from here https://retropie.org.uk/download/ and flashed it onto my SD. Hope this helps

mitu

Is there any firewall between your PI and your PC ? Can you run - from a command line on Windows - a ping and get a successful connection ?

ping <retropie_ip>

cyperghost

@tmshll do You see an IP if you go to RETROPIE --> WiFi?
Furthermore how did you enable SSH service and entered WiFi credentials?
Is there a Proxy or Firewall in your network?

tmshll

@mitu Hi, just tried a few pings, got the following:

Ping: transmit failed. General failure

mitu

How are you typing the command ? This error happens when your PC is not connected to the network or has limited connectivity.

tmshll

@cyperghost Hi,

I created an SSH file (blank txt file and then deleted the extension) I also made sure SSH was enabled via interfacing options through Retropie.

As for setting up the WiFi I created a wpa_supplicant.conf file on my SD, and input my details (am I right in thinking my SSID is the same as my WiFi network name on my router?) I think this worked as I tested the WiFi by downloading extra splash screens via the GPi case.

tmshll

@mitu okay, just reset my WiFi and got a response from my GPi (Reply from 192.168.1.7: bytes=32 time=48ms TTL=64)

Should I try PuTTY again?

tmshll

@tmshll @mitu just tried putty and got the message:

Remote side unexpectedly closed network connection

mitu

Are you sure you don't have a firewall on your router/Wifi AP ?

tmshll

@mitu how could I check if there's one in place? Ty

mitu

Check on your Router/AP web management page - see if any firewall is configured in their settings.

cyperghost

@tmshll said in GPi SSH/PuTTY issues:

@cyperghost Hi,

I created an SSH file (blank txt file and then deleted the extension) I also made sure SSH was enabled via interfacing options through Retropie.

As for setting up the WiFi I created a wpa_supplicant.conf file on my SD, and input my details (am I right in thinking my SSID is the same as my WiFi network name on my router?) I think this worked as I tested the WiFi by downloading extra splash screens via the GPi case.

Yes ... that seems correct.

192.168.1.7

Yes, that's your IP ....

@mitu
Windows is very weak in handling ports ;)
You can use pping and a command like PPing retropie 22 to determine if port 22 is open.

@tmshll In your example the call would be PPing 192.168.1.7 22 to check connection to SSH port 22