Search Engine: Elastic
  • Article for your preferred language does not exist. Below is international version of the article.

Article ID: 115802, created on Mar 24, 2013, last review on Sep 9, 2015

  • Applies to:
  • Operations Automation

Troubleshooting Linux FTP service

Disclaimer: the article is applicable to the Standard Linux Shared Hosting, not to Linux Shared Hosting NG. Refer to the article for information about Linux Shared Hosting NG in POA.

The common problems with FTP service
  • Failed/pending POA tasks - ProFTPD configuration files were not updated properly
  • Services not started - FTP access to webspace does not work
  • Firewall configuration - FTP access to webspace does not work

Use the steps below to troubleshoot the problems with FTP access to customers' webspaces.

1. Check if ProFTPD service is running on a server where customer's webspace is located: # /etc/init.d/proftpd service status
2. Start the FTP service if it is not running or hung: # /etc/init.d/proftpd service restart
3. Check if FTP service process is running: # ps ax | grep proftpd
  712 ?        SLs    0:03 proftpd: (accepting connections)

4. Check if the FTP port 21 is being listened to on a server using the netstat utility:
# netstat -antp | grep :21
tcp        0      0*      LISTEN      712/proftpd

5. Check firewall rules in datacenter and make sure that FTP port 21 is accessible from the Internet for all POA-managed Linux Shared Hosting servers where customers' webspaces are hosted. Refer to the PA Firewall Configuration Guide for the recommended settings -

6. If a particular user cannot connect to a webspace via FTP check if the user is present in the /usr/local/pem/ftp/ftp_auth/VHOST_ID/passwd file and correct group ownership configured for it (user must belong to the pemcln group). Try to change password of the problem FTP user in POA Customer CP, it will update corresponding FTP user settings.

See the main Knowledgebase article #115790 Website Hosting: General information, Best Practices and Troubleshooting for more information.

caea8340e2d186a540518d08602aa065 5356b422f65bdad1c3e9edca5d74a1ae e12cea1d47a3125d335d68e6d4e15e07

Email subscription for changes to this article
Save as PDF