systemctl enable ssh

and subsequently rebooting

doesn't auto-start sshd.

Because: The OS tries to start it before
the network is online.

this can be checked with
journalctl -b

I also checked it with a stable Debian-Instance.
It's the same there, too.

There was a time when this worked, before.

Can anybody confirm this?

After booting and login, OpenSSH can be
started flawlessly via

systemctl start ssh

Only boot-time activation seems to be broken.

Well OpenSSH works again…

But only because I re-enabled

this systemd unit:

ssh.socket

I was not able to get OpenSSH
, i.e. the ssh.service

to start at boot-time
without socket activation.

Of course, I could have set
TimeOuts or Retries to Infinity,
but this would be idiotic.

This systemd stuff is crazily over-complicated. It's insane.