From 5113c2fe58c0136734170772259dfc9edb382163 Mon Sep 17 00:00:00 2001 From: MickLesk Date: Tue, 21 Jul 2026 23:23:25 +0200 Subject: [PATCH] Work around nextcloudpi's broken ssh.socket restart on Debian 13 Debian 13's openssh-server ships socket-activated by default. NCP's own bin/ncp/NETWORKING/SSH.sh detects that (systemctl is-active ssh.socket) but then runs "systemctl restart ssh" in that branch instead of reloading, which collides with the port ssh.socket already holds and fails with "Job for ssh.service failed" (#15944). Switch the container to classic ssh.service before handing off to their installer so it takes the safe "systemctl reload ssh" branch instead. --- install/nextcloudpi-install.sh | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/install/nextcloudpi-install.sh b/install/nextcloudpi-install.sh index 1b30a173b..5e71d55d2 100644 --- a/install/nextcloudpi-install.sh +++ b/install/nextcloudpi-install.sh @@ -24,6 +24,11 @@ if [[ ! "$CONFIRM" =~ ^([yY][eE][sS]|[yY])$ ]]; then exit 10 fi +msg_info "Switching SSH to classic (non-socket-activated) mode" +systemctl disable --now ssh.socket &>/dev/null || true +systemctl enable --now ssh &>/dev/null || true +msg_ok "Switched SSH to classic mode" + msg_info "Installing NextCloudPi (Patience)" $STD bash <(curl -fsSL https://raw.githubusercontent.com/nextcloud/nextcloudpi/master/install.sh) msg_ok "Installed NextCloudPi"