Fresh install retropie 4.2 cannot ssh or sftp

EvilWayz

@obsidianspider said in Fresh install retropie 4.2 cannot ssh or sftp:

Enable SSH on a headless Raspberry Pi

For headless setup, SSH can be enabled by placing a file named 'ssh', without any extension, onto the boot partition of the SD card. When the Pi boots, it looks for the 'ssh' file. If it is found, SSH is enabled, and the file is deleted. The content of the file does not matter: it could contain text, or nothing at all.

https://www.raspberrypi.org/documentation/remote-access/ssh/

Berryboot doesn't allow that.

Workaround is as follows:

Get out of Emulation station by hitting shift+ F4. That will drop you to terminal
then type the following:

cd /
sudo mkdir boot
sudo mount /dev/mmcblk0p1 /boot
exit

That should get you back to the Emulation Station Retropie menu. Click on raspi-config and then select the option for Interfacing options. Click on SSH and click enable.

Once you reboot you should be good to go.

BuZz

@EvilWayz or just do update-rc.d ssh enable (and reboot).

cgeyik

I am unable to get SSH working. After enabling it i get the following error message from Putty: Network error Software caused connection abort.

I tried to connect via my android phone and the message i get there is: session.connect: java.io.IOExeption: End of IO Stream Read.

Any help would be appriciated.

tmak

Hey, so. I updated to the latest Retro pie 4.2. I enabled ssh Connect. So I am now able to connect to the raspberry via filezilla,. However it won't let me delete or move roms to different folders. Has anyone had this issue and is there a fix?

Thanks,

Swagman89

@BuZz @herb_fargus can one of you guys close this thread so we can stop having other people hijack this trainwreck? That way they can make their own threads and not read the README.

edmaul69

@Swagman89 as the person who created this thread, i see nothing that people have asked that arent related to ssh issues and 4.2. Just because i managed to fix it by just enabling ssh, there are others who havent and if they create a new post they will probably get told the exact same thing. I would prefer keeping it contained to one thread.

Swagman89

@edmaul69 Just figured it went against the rules seeing as there have been multiple people say they are having the same issue. Which could all be fixed by reading the documentation.

edmaul69

@Swagman89 the problem is that some people have done what i have done and stll have issues. The problem is that this is all new to 4.2 due to raspberrypi.or making changes to pixel because of hackers using "internet of things" devices to take down websites. So even when i asked i didnt think to look because i have done so much retropie stuff and never saw this before so it didnt make sense why it wasnt working and doing a search didnt help.

Swagman89

@edmaul69 not to be rude but I'm pretty sure it was in the release notes/changelog for 4.2. I feel confident that 99.9% of all changes made to RetroPie are documented. Plus if other people are having issues after they added the file to enable ssh then they should make a new thread or open a problem report on github. Makes it easier to find with a search imo.

PetroRie

Why did they disable it on default?

edmaul69

@PetroRie raspberrypi.org disabled it in pixel because hackers are using peoples "internet of things" devices that use a common password to take down entire websites. So reluctantly the felt it was something that had to be done. So when you enable it and you drop to commandline you will notice at the top that it tells you to change your password. This is all to protect you and your device.