So – kind of unrelated but I’m running Ubuntu 24.04 within a TrueNas Core VM – by default the sshd runs via socket activation. If I don’t manually VNC into the TrueNAS Core VM and login (first) – I can’t remotely ssh into the machine. After I manually login at the console – then I’m able to ssh into the machine. Is this the intended behaivor because it is very very annoying.
That sounds like it is more related to the availability of your /home directory, and not really ssh. Do you have something like home automounting, or encrypted home?
What happens when you try?
Honestly it just hangs — nothing happens. Because I’m running within a VM, I need to use the manual VNC to login. After that things tend to work
**Update - I just changed the sshd profile so it just runs straight from startup and not from socket activation and the entire problem went away in terms of not being able to login remotely. I’m sure there is a reason why the socket activation didn’t work but I just didn’t have the time to debug the problem.
1 Like