xtreamsolutions
New member
- Joined
- Jan 10, 2026
- Messages
- 2
Operating System: Debian GNU/Linux 13 (trixie)
Kernel: Linux 6.12.57+deb13-cloud-amd64
Architecture: x86-64
Hardware Vendor: QEMU
Hardware Model: Standard PC _i440FX + PIIX, 1996_
Firmware Version: rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org
Firmware Date: Tue 2014-04-01
Firmware Age: 11y 9month 1w 3d
DirectAdmin 1.691
Persistent "sshd is down" Alerts Despite Custom Service
DirectAdmin sends hourly alerts that "the service 'sshd' on server is currently down" for the past 30 days. This started after changing SSH to a custom systemd service (sshd-tailscale.service) on port 2xxx.
# /usr/local/directadmin/conf/directadmin.conf
sshd_port=2xxx
sshd=sshd-tailscale
# /usr/local/directadmin/data/admin/services.statussshd=ON
Custom Service Script Created
Kernel: Linux 6.12.57+deb13-cloud-amd64
Architecture: x86-64
Hardware Vendor: QEMU
Hardware Model: Standard PC _i440FX + PIIX, 1996_
Firmware Version: rel-1.17.0-0-gb52ca86e094d-prebuilt.qemu.org
Firmware Date: Tue 2014-04-01
Firmware Age: 11y 9month 1w 3d
DirectAdmin 1.691
Persistent "sshd is down" Alerts Despite Custom Service
DirectAdmin sends hourly alerts that "the service 'sshd' on server is currently down" for the past 30 days. This started after changing SSH to a custom systemd service (sshd-tailscale.service) on port 2xxx.
Current Configuration
# /usr/local/directadmin/conf/directadmin.conf
sshd_port=2xxx
sshd=sshd-tailscale
# /usr/local/directadmin/data/admin/services.statussshd=ON
Custom Service Script Created
Code:
# /usr/local/directadmin/scripts/custom/service_sshd.sh
#!/bin/bash
case "$1" in
start|stop|restart|reload) systemctl "$1" sshd-tailscale ;;
status) systemctl is-active --quiet sshd-tailscale && echo "sshd-tailscale is running" || { echo "sshd-tailscale is not running"; exit 1; } ;;
esac
Code:
$ systemctl status sshd-tailscale.service
● sshd-tailscale.service - OpenSSH server daemon (Tailscale-aware)
Loaded: loaded (/etc/systemd/system/sshd-tailscale.service; enabled)
Active: active (running)
$ ss -tlnp | grep 2xxx
LISTEN 0 128 0.0.0.0:2xxx 0.0.0.0:* users:(("sshd",pid=2385,fd=6))
Questions
- Is the custom script location and naming correct for DirectAdmin 1.691?
- Is there an additional step required for DirectAdmin to use the custom service script?
- How can I clear the existing cached alerts?
- Is there a log file where I can verify DirectAdmin is using my custom script?
Last edited: