Geofferic
Posts: 4
Joined: Wed Jul 17, 2019 11:43 pm

Can't get SSH to enable on headless RPi3.

Wed Jul 17, 2019 11:48 pm

So I'm imaging the SD with Raspbian Buster.

I place an empty file called "ssh" in the boot partition, not the boot folder.

Hook the sucker up. I can ping it, but ssh is refused:
NaCl plugin exited with status code 255.
I have re-imaged and added the ssh file many times.

When I boot the Pi, the ssh file does disappear, so I assume it's at least trying to setup ssh.

I don't know enough about Debian to manually setup ssh, but I can edit everything on the boot partition and the ext partition, so if someone can point me in the correct direction, that'd be awesome.

I'm also unsure of further troubleshooting to try, so if anyone can help with that, that would also be great!

Thanks so much!

EDIT: FWIW I'm using the Buster Lite image.
Last edited by Geofferic on Thu Jul 18, 2019 1:51 am, edited 1 time in total.

Andyroo
Posts: 4135
Joined: Sat Jun 16, 2018 12:49 am
Location: Lincs U.K.

Re: Can't get SSH to enable on headless RPi3.

Thu Jul 18, 2019 12:17 am

Can you run to get verbose error and see if that gives a clue?
Need Pi spray - these things are breeding in my house...

Geofferic
Posts: 4
Joined: Wed Jul 17, 2019 11:43 pm

Re: Can't get SSH to enable on headless RPi3.

Thu Jul 18, 2019 1:49 am

Andyroo wrote:
Thu Jul 18, 2019 12:17 am
Can you run to get verbose error and see if that gives a clue?

Code: Select all

OpenSSH_for_Windows_7.6p1, LibreSSL 2.6.4
debug1: Connecting to 192.168.0.25 [192.168.0.25] port 22.
debug1: connect to address 192.168.0.25 port 22: Connection refused
ssh: connect to host 192.168.0.25 port 22: Connection refused
I noticed that others have had trouble with the sensehat connected, but I have nothing attached other than ethernet.

EDIT: FWIW I'm using the Buster Lite image. I will try with a different Buster image and report back.

Andyroo
Posts: 4135
Joined: Sat Jun 16, 2018 12:49 am
Location: Lincs U.K.

Re: Can't get SSH to enable on headless RPi3.

Thu Jul 18, 2019 1:56 am

You could try fing https://www.fing.com/ and see if the port is open.

Worth double checking the Pi IP address - not that I’ve ever tried to ssh into the machine I’m on :oops: :lol:

Do you have a firewall set up on the Pi?
Need Pi spray - these things are breeding in my house...

Geofferic
Posts: 4
Joined: Wed Jul 17, 2019 11:43 pm

Re: Can't get SSH to enable on headless RPi3.

Thu Jul 18, 2019 3:06 am

Welp, all Buster images fail as does the Jessie image - which it was running fine before.

Now I wonder if there's a firewall issue.

Geofferic
Posts: 4
Joined: Wed Jul 17, 2019 11:43 pm

Re: Can't get SSH to enable on headless RPi3.

Thu Jul 18, 2019 4:56 am

RESOLVED.

So I had moved across the Atlantic ocean and in the process some routers got moved around, and apparently the ASUS AC3200 I have had some kinda firmware problem. Updated and bingo, all is well.

Thank you so much for your patience!

User avatar
DougieLawson
Posts: 35784
Joined: Sun Jun 16, 2013 11:19 pm
Location: Basingstoke, UK
Contact: Website Twitter

Re: Can't get SSH to enable on headless RPi3.

Thu Jul 18, 2019 5:42 am

Geofferic wrote:
Wed Jul 17, 2019 11:48 pm

I place an empty file called "ssh" in the boot partition, not the boot folder.
Is this NOOBS or plain Raspbian?

With plain Raspbian you write the SDCard with Etcher (Linux, Mac or Windows) or DD (Linux) or Win32DiskImager (Windows). Eject it. Re-insert it and touch a file on the first partition (Linux) or echo "" > f:\ssh (Windows assuming the first partition appears as F:).

If the SDCard has NOOBS I've no idea how you set it up headless with SSH. Don't use NOOBS on headless systems.

If you can connect a keyboard/mouse then when Raspbian has booted use

sudo touch /boot/ssh && reboot

or
sudo systemctl enable ssh
sudo systemctl start ssh
Note: Having anything humorous in your signature is completely banned on this forum. Wear a tin-foil hat and you'll get a ban.

Any DMs sent on Twitter will be answered next month.

This is a doctor free zone.

Return to “Troubleshooting”