I had this happen to me as well as the original poster. I also disabled socket authentication using the steps from the thread attached by the original poster to get access to the server again via SSH. Here is the unattended-upgrades log:
Log started: 2024-11-09 06:52:08 Preconfiguring packages ... Preconfiguring packages ... (Reading database ... 121348 files and directories currently installed.) Preparing to unpack .../openssh-sftp-server_1%3a9.6p1-3ubuntu13.7_amd64.deb ... Unpacking openssh-sftp-server (1:9.6p1-3ubuntu13.7) over (1:9.6p1-3ubuntu13.5) ... Preparing to unpack .../openssh-server_1%3a9.6p1-3ubuntu13.7_amd64.deb ... Unpacking openssh-server (1:9.6p1-3ubuntu13.7) over (1:9.6p1-3ubuntu13.5) ... Preparing to unpack .../openssh-client_1%3a9.6p1-3ubuntu13.7_amd64.deb ... Unpacking openssh-client (1:9.6p1-3ubuntu13.7) over (1:9.6p1-3ubuntu13.5) ... Setting up openssh-client (1:9.6p1-3ubuntu13.7) ... Setting up openssh-sftp-server (1:9.6p1-3ubuntu13.7) ... Setting up openssh-server (1:9.6p1-3ubuntu13.7) ... Processing triggers for man-db (2.12.0-4build2) ... Processing triggers for ufw (0.36.2-6) ... Restarting services... Service restarts being deferred: /etc/needrestart/restart.d/dbus.service systemctl restart getty@tty1.service systemctl restart serial-getty@ttyS0.service systemctl restart systemd-logind.service systemctl restart unattended-upgrades.service No containers need to be restarted. No user sessions are running outdated binaries. No VM guests are running outdated hypervisor (qemu) binaries on this host. Log ended: 2024-11-09 06:52:14 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to openssh in Ubuntu. https://bugs.launchpad.net/bugs/2087551 Title: OpenSSH server config broken on unattended update Status in openssh package in Ubuntu: Incomplete Bug description: My server performed unattended update of openssh-server from 1:9.6p1-3ubuntu13.5 to 1:9.6p1-3ubuntu13.7, and after this I could not access ssh anymore, connection refused. Following the steps at the bottom of this post to use non-socket- based-activation has allowed me to connect to the server again: https://discourse.ubuntu.com/t/sshd-now-uses-socket-based-activation- ubuntu-22-10-and-later/30189 I suspect this is related to using a non-default port, although the systemd socket configuration appeared to exist with correct values, as well as the custom port value in sshd_config, before making the above change. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: openssh-server 1:9.6p1-3ubuntu13.7 ProcVersionSignature: Ubuntu 6.8.0-48.48-generic 6.8.12 Uname: Linux 6.8.0-48-generic x86_64 ApportVersion: 2.28.1-0ubuntu3.1 Architecture: amd64 CasperMD5CheckResult: unknown CloudArchitecture: x86_64 CloudBuildName: server CloudID: configdrive CloudName: configdrive CloudPlatform: configdrive CloudSerial: 20231014 CloudSubPlatform: config-disk (/dev/vdb) Date: Fri Nov 8 13:13:51 2024 ProcEnviron: LANG=C.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=tmux-256color SourcePackage: openssh UpgradeStatus: Upgraded to noble on 2024-06-04 (157 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openssh/+bug/2087551/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
