tower-diagnostics-20250310-2038.zip

 

I have disabled SSH from settings > ssh, by stopping it and setting Enable SSH Service to "No". Looking though my logs for different things and I keep seeing it listening on port 22 and I have not enabled it myself. When I go to settings > ssh, it is indeed running and I stop it. How can I pin down what is starting it? Can dockers turn on my SSH service somehow? Is SSH service automatically enabled after a reboot even if I've specifically set it to disabled? port 22 is not open to the internet but I'd still feel safer if ssh was not running when I don't need it to be.

you can run a user script plugin to kill the service at start of the array.

Yes, some dockers like sftp docker run ssh and may use ssh for inner docker communication and process. (my syss log show this then stoped then shown agan due to sftp docker instance...)

Yes, some plugins like ssh plugin and unriad connect may enable the service for secure communication.

At boot Unraid v7 has a instance of testing and checkin sshd and will temp start then check ssh option and disable the service.

user script to kill:

 

#!/bin/bash
# User Script to Kill and Disable SSH in Unraid (Slackware-based)

echo "Stopping all SSH connections..."

# Kill all active SSH processes
pkill -9 sshd
pkill -9 ssh

echo "Disabling SSH service..."

# Remove execute permissions to prevent SSH from starting
chmod -x /etc/rc.d/rc.sshd

# Ensure SSH is disabled on boot
if [[ -f /boot/config/go ]]; then
    sed -i '/rc.sshd/d' /boot/config/go
fi

echo "SSH has been disabled. To re-enable, manually restore permissions to /etc/rc.d/rc.sshd"

Run once and it will kill any and all ssh. this will also add data to your go file to disable the service at boot.

Edited March 16, 20251 yr by bmartino1
run once script

I see. Thank you.