Issue with starting Proftpd Version: 1.3.3g (maint) on CPanel servers

We can solve the issue with starting proftpd using following steps when you receive this error on debugging: (unable to determine IP address of ‘’)


[root@vps init.d]# service proftpd start
Starting proftpd: [FAILED]


Perform Configuration Check
When making changes to the configuration file, it is often helpful to make sure that your changes are valid. The easiest way to do this is to do an informative syntax check:

  proftpd -td10

The -t option directs the server to only do a syntax check, to parse the configuration file but stop before actually starting its operations as a server. The -d10 will cause the server to display debugging messages during this testing of the configuration file. Another useful command is:

  proftpd -c /path/to/new/config/file -td10

which lets you test the syntax of some new configuration file before it is put into production. If you are still having problems, and you have verified that your proftpd.conf is correct, the next step is see what debugging messages are generated during an FTP session, as described next.


[root@vps init.d]# proftpd -td10
Checking syntax of configuration file
– using TCP receive buffer size of 87380 bytes
– using TCP send buffer size of 16384 bytes
– testing Unix domain socket using S_ISFIFO
– testing Unix domain socket using S_ISSOCK
– using S_ISSOCK macro for Unix domain socket detection
– mod_tls/2.4.2: using OpenSSL 1.0.1e-fips 11 Feb 2013
– ROOT PRIVS at mod_core.c:304
– retrieved UID 0 for user ‘root’
– retrieved GID 0 for group ‘root’
– loading ‘mod_sql.c’
– loading ‘mod_sql_mysql.c’
– loading ‘mod_quotatab.c’
– loading ‘mod_quotatab_sql.c’
– RELINQUISH PRIVS at mod_core.c:326
– warning: unable to determine IP address of ‘’
– error: no valid servers configured
– Fatal: error processing configuration file ‘/etc/proftpd.conf’


[root@vps init.d]# cat /etc/hosts localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6               ==>> Adding this line to host file will solve the issue.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s