Unable to SSH or SFTP After Upgrade

Using Lish via browser (my only option), I notice:

root@Hephaestus:~# sudo service ssh status
● ssh.service
Loaded: not-found (Reason: No such file or directory)
Active: inactive (dead)

The problem is, I can't install it via Lish with no networking. Also, why was it unistalled during an upgrade and after a reboot, locking me out?

This may be related to a host update that we've recently made. You'll need to find your network interfaces to confirm that this is what's causing an issue with networking. You can find this by running:

ip link show

There's a good chance that you just need to enable Network Helper.

Thanks. It actually was enabled and I disabled and rebooted, to try every available path. I forgot to re-enable. Doing it now.

Rebooted, same effect. I noticed in the job queue: Network Helper did not run: could not reliably determine distribution or distribution version

With Lish, I ran: root@Hephaestus:~# ip link show
1: lo: <loopback,up,lower_up> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAUL0
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: dummy0: <broadcast,noarp> mtu 1500 qdisc noop state DOWN mode DEFAULT group 0
link/ether be:c9:4b:25:a0:c5 brd ff:ff:ff:ff:ff:ff
3: eth0: <broadcast,multicast,up,lower_up> mtu 1500 qdisc fq_codel state UP mod0
link/ether f2:3c:91:55:ed:9a brd ff:ff:ff:ff:ff:ff
4: teql0: <noarp> mtu 1500 qdisc noop state DOWN mode DEFAULT group default qle0
link/void
5: tunl0@NONE: <noarp> mtu 1480 qdisc noop state DOWN mode DEFAULT group defaul0
link/ipip 0.0.0.0 brd 0.0.0.0
6: gre0@NONE: <noarp> mtu 1476 qdisc noop state DOWN mode DEFAULT group default0
link/gre 0.0.0.0 brd 0.0.0.0
7: gretap0@NONE: <broadcast,multicast> mtu 1462 qdisc noop state DOWN mode DEFA0
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
8: erspan0@NONE: <broadcast,multicast> mtu 1450 qdisc noop state DOWN mode DEFA0
link/ether 00:00:00:00:00:00 brd ff:ff:ff:ff:ff:ff
9: ip_vti0@NONE: <noarp> mtu 1480 qdisc noop state DOWN mode DEFAULT group defa0
link/ipip 0.0.0.0 brd 0.0.0.0
10: ip6_vti0@NONE: <noarp> mtu 1364 qdisc noop state DOWN mode DEFAULT group de0
link/tunnel6 :: brd ::
11: sit0@NONE: <noarp> mtu 1480 qdisc noop state DOWN mode DEFAULT group defaul0
link/sit 0.0.0.0 brd 0.0.0.0
12: ip6tnl0@NONE: <noarp> mtu 1452 qdisc noop state DOWN mode DEFAULT group def0
link/tunnel6 :: brd ::
13: ip6gre0@NONE: <noarp> mtu 1448 qdisc noop state DOWN mode DEFAULT group def0
link/gre6 00:00:00:00:00:00:00:00:00:00:00:00:00:00:00:00 brd 00:00:00:00:00</noarp></noarp></noarp></noarp></noarp></broadcast,multicast></broadcast,multicast></noarp></noarp></noarp></broadcast,multicast,up,lower_up></broadcast,noarp></loopback,up,lower_up>

@watrick Is there a way to roll this linode back to this morning or yesterday? I've been wrestling and reading your support docs and posting for several hours.

The only way to roll back a Linode would be to use an available backup from either our Backups or another backup that you've set up.

I'd recommend reviewing the dmesg log to check if there was any messages in the boot job that would point you in the the right direction. This can be done by running:

sudo dmesg

There may be messages in there that can help illuminate issues that began with the latest boot.