I also had this behavior.
The problem in my case was that ssh.socket got enabled somehow.
When disabling ssh.socket, ssh.service does start normally on boot.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.