SSH cannot be enabled after installation

Had the same issue - i flashed system again and it worked. Was looking for many answers but there is not to many other options.

I have now flashed this five (5) times on a two different brand new SD cards with no luck.

I believe this proves that it is rather compatibility/software than hardware issue.

What are my options to investigate this further? Or should I try some other distributions suitable for s912

Also recorded UI misbehavior but video was 102MB and therefore was unable to attach it here.

Use a Filehosting site like Google Drive or Mega NZ and supply link.
Different issue to the SSH topic here so open a new one.

Please upload logs with a link.
Devs hate downloading logs.

Can you please confirm you use 1 Router in your Network setup ?

1. # Generated by Connection Manager

2. nameserver

3. nameserver

1. Kernel IP routing table

2. Destination     Gateway         Genmask         Flags   MSS Window  irtt Iface

3.         UG        0 0          0 eth0

4.   U         0 0          0 eth0

5. UH        0 0          0 eth0

6. UGH       0 0          0 eth0

7. UGH       0 0          0 eth0

As you say it doesn’t really look like SSH is running based on the netstat logs and it’s not possible to tell based on the networking logs why it doesn’t turn on.

A bit far fetched but I’ve seen the CoreELEC Configuration menus behave strangely due to some poorly coded video addon. But I suppose since you’ve flashed it multiple times you’ve already tried to enable SSH right after clean install and before installing any additional addons?

I just copped the port 22 refused connection on Vim2 S912 fresh Nightly install SD Card CE
I did a Hard Reset via the CE Configuration and enabled SSH Via the wizard using default Password and connection was established after that.
We’re looking into it.

1 Like

Yes, there is only one router, but DNS services are set statically to gain better connection

Thanks for the workaround,
I did the hard reset as well and got SSH working straight away when running installation wizard.

Video with the issue on clean first installation:

Thank You @vipasane
First thing i noticed from your video is that SMB is not Enabled by Default.
It should have been Enabled by Default.
Something is definitely wrong with CE configurator after your install.
Again we’re looking into it.

Well actually it is enabled and working but as I wrote before UI will show it as disabled when enabling ssh fails, therefore I left the part that I visit another wizard step to regain real value of smb being enabled.

I had similar problem (no sshd accessible on 22 port on CoreELEC running from CF card). The reason is this:

journalctl -u sshd

Jan 01 00:00:25 CoreELEC ssh-keygen[3078]: ssh-keygen: generating new host keys: RSA Could not save your public key in /storage/.cache/ssh/ssh_host_rsa_key.Kp3BJI6nwD: No such file or directory

With absence of sshd on CoreELEC host, I’ve been able to login via ‘Web SSH Terminal’ (in addon/services/) which is accessible on port 11111 from web browser.
mkdir /storage/.cache/ssh
systemctl start sshd

That is it.

1 Like

I had the very same issue and can fully confirm that this was the root cause. I used the same solution (login via webssh addon and then create the missing folder). Thanks for pointing the out!

Hello @kostaman - first of all thank you for all the work you are doing to great product available for us! :slight_smile:

Recently I’ve been hit with this missing SSH folder issue on a new installation (9.2.2, mecool m8s pro+ box) - have you been able to identify the root cause since your post back in January?

I’ve not been back to this thread until now.

I’ve not had this happen on the last few fresh installs i’ve done.

I thought it was resolved.

Maybe a weird race condition?

Can you guys add an extra verification into the startup / SSH enabler script which checks for that folder (/storage/.cache/ssh) being successfully created, and if not, then retry creating it?

Will be added in next nightly build.

1 Like

THANK YOU! :slight_smile:

I happened by here upon having the same issues enabled SSH on a new installation. I realized when I first booted the device I had no network connection set up until the kodi/coreelec screen had come up and the wizard talked about network setup. I then plugged an ethernet cable in and could not get SSH to work, despite having a valid IP from my DHCP server.

However, upon redoing my steps of installation and booting up with the network cable attached, all worked fine.

So, making sure you have a network cable attached may help alleviate this problem from occuring.