GICT knowledge base
Start or Stop ProFTPD Through the Correct Service Manager
Published
Start or stop ProFTPD only after confirming that it is the intended FTP daemon and identifying how the installed system manages it. A cPanel-managed FTP service, a standalone systemd unit and an older init script are not interchangeable control paths.
Identify the service and impact
Use authorized administrative access, check the active daemon and current transfers, and retain recovery access. Stopping FTP interrupts that service; it does not stop or configure SSH/SFTP. A restart is not a repair for an unexplained authentication, TLS or passive-data problem.
Standalone systemd example
Only if the installed unit is actually named proftpd.service, these are the corresponding operations. Status is diagnostic; start, stop and restart change the live service and require appropriate privileges. Do not execute all four as a troubleshooting sequence.
systemctl status proftpd.service
systemctl start proftpd.service
systemctl stop proftpd.service
systemctl restart proftpd.service
For an older system that really installs an executable /etc/init.d/proftpd script, its documented start/stop actions may apply. Do not create that path or install an obsolete package merely to match an old tutorial.
cPanel-managed service
Use the installed WHM FTP/service controls and cPanel’s documented FTP service mechanism, not a guessed standalone unit. The documented restart wrapper is /usr/local/cpanel/scripts/restartsrv_ftpserver. Confirm the selected daemon and maintenance scope before requesting a restart; do not disable monitoring globally or change daemons to force a restart.
Verify recovery
Inspect service status and logs, then verify authorized encrypted login, directory listing and a harmless scoped transfer. A running process or open control port alone does not prove the TLS/data path or account permissions work.
References: upstream systemctl manual and cPanel service monitoring and restart wrapper.
Reviewed October 16, 2026. Command syntax and inert argument checks only; no FTP daemon was started, stopped or restarted.
Related guides
How to Restrict an SSH Key to One Command
Restrict an SSH key to one command with authorized_keys options. Protect the command and check that unwanted shell and forwarding access are denied.
Linux and CommandsSelf-Hosted Video Processing With FFmpeg: A Practical Guide
Learn how to self-host video processing on a VPS using FFmpeg, with practical commands for conversion, compression, thumbnails, and automated workflows.
Linux and CommandsHow to use nohup: Commands in Linux That Survive Terminal Closes
Keep commands running after you close the terminal. nohup examples with wget, Python, rsync, and Docker on any VPS.
Linux and CommandsHow to Fix “Too Many Open Files” Error on Linux Servers
Learn how to fix the "Too Many Open Files" error on Linux servers by understanding file descriptors, adjusting limits, and diagnosing leaks effectively.
