Troubleshooting cPanel FTP Connectivity Issues
If your FTP connection through cPanel fails, here are a few things you can do to troubleshoot the problem before calling customer support.
- Log into your server using SSH.
- At the command line, type
su -. This gives you root access.
For more information on using root access on your server, see Accessing Your Virtual Private Server (VPS) Using SSH, or How Can I Log in as Root on my Virtual Private Server (VPS)?
Verify That the Issue Exists on the Server
If the server does not have a firewall and/or IPTABLES are not running, it is unlikely that the problem exists on the server. It's recommended to continue troubleshooting possible problems with your local computer or Internet connection.
If you do have a firewall or IPTABLES running, run the following command:
If the response is as follows, the issue may be related to configuration changes to the server's IPTABLES or firewall configuration:
220---------- Welcome to Pure-FTPd [TLS] ----------
220-You are user number 1 of 50 allowed.
220-Local time is now 07:20. Server port: 21.
220 You will be disconnected after 15 minutes of inactivity.
Name(localhost:user):
If you get this response, it means that the FTP server is likely not running, or may be running, but the process has failed. Pure-ftpd runs as it's own process, try restarting the service. Continue with these troubleshooting steps:
Make Sure pure-ftpd is Running and Listening on Port 21
To verify that pure-ftpd is running and the server is listening on port 21.
pure-ftpd (pid 3302) is running...
+------+---------+-------+------+-------------------------------------------+ | PID | Login |For/Spd| What | File/IP | +------+---------+-------+------+-------------------------------------------+
[root@host ~]# lsof-i tcp:21
COMMAND PID USER FD TYPE DEVICE SIZE NODE NAME
pure-ftpd 3302 root 4u IPv4 574378144 TCP *:ftp (LISTEN)
Run the FTP localhost command again.
This is the most common server-side issue with pure-ftpd. If this procedure did not resolve the issue, you can view the log to find other possible reasons for the failure.
Check the Errors Log
If the issue is still not resolved, you can view the logs to see what else might be causing the problem. You can view your server's error logs by running the following command:
NOTE: Copying the text of an error into a search engine might produce possible solutions for problems that you are unsure how to resolve.
