PROFTPD not connecting from FTP Client

Posted February 5, 2017 7.5k views
Configuration ManagementUbuntu 16.04

So I followed the Proftpd guide and installed ProFTPD on my droplet.

I can connect no problem from SSH. However I can’t access FTP from an FTP client or a browser.

I understand that I should use SFTP and I’m using that but I need access via FTP for this droplet because certain software that needs to upload files to the server only works through FTP.

I have 3 domains on the droplet, one of which is
I’m using forge as username and forge’s root password (Laravel Forge created this user to manage the servers).

What am I missing here? As I mentioned, SSH command line access works fine when I SSH into the droplet but not from browser.

Many thanks.

Here is the proftpd conf file:

/etc/proftpd/proftpd.conf – This is a basic ProFTPD configuration file.

To really apply changes, reload proftpd after modifications, if

it runs in daemon mode. It is not required in inetd/xinetd mode.

Includes DSO modules

Include /etc/proftpd/modules.conf

Set off to disable IPv6 support which is annoying on IPv4 only boxes.

UseIPv6 on

If set on you can experience a longer connection delay in many cases.

IdentLookups off

ServerName “”
ServerType standalone
DeferWelcome off

MultilineRFC2228 on
DefaultServer on
ShowSymlinks on

TimeoutNoTransfer 600
TimeoutStalled 600
TimeoutIdle 1200

DisplayLogin welcome.msg
DisplayChdir .message true
ListOptions “-l”

DenyFilter *.*/

Use this to jail all users in their homes

DefaultRoot ~

Users require a valid shell listed in /etc/shells to login.

Use this directive to release that constrain.

RequireValidShell off

Port 21 is the standard FTP port.

Port 21

In some cases you have to specify passive ports range to by-pass

firewall limitations. Ephemeral ports can be used for that, but

feel free to use a more narrow range.

PassivePorts 49152 65534

If your host was NATted, this option is useful in order to

allow passive tranfers to work. You have to use your public

address and opening the passive ports used on your firewall as well.


This is useful for masquerading address with dynamic IPs:

refresh any configured MasqueradeAddress directives every 8 hours

<IfModule mod_dynmasq.c>

DynMasqRefresh 28800


To prevent DoS attacks, set the maximum number of child processes

to 30. If you need to allow more than 30 concurrent connections

at once, simply increase this value. Note that this ONLY works

in standalone mode, in inetd mode you should use an inetd server

that allows you to limit maximum number of processes per service

(such as xinetd)

MaxInstances 30

Set the user and group that the server normally runs at.

User proftpd
Group nogroup

Umask 022 is a good standard umask to prevent new files and dirs

(second parm) from being group and world writable.

Umask 022 022

Normally, we want files to be overwriteable.

AllowOverwrite on

Uncomment this if you are using NIS or LDAP via NSS to retrieve passwords:

PersistentPasswd off

This is required to use both PAM-based authentication and local passwords

AuthOrder modauthpam.c* modauthunix.c

Be warned: use of this directive impacts CPU average load!

Uncomment this if you like to see progress and transfer rate with ftpwho

in downloads. That is not needed for uploads rates.

UseSendFile off

TransferLog /var/log/proftpd/xferlog
SystemLog /var/log/proftpd/proftpd.log

Logging onto /var/log/lastlog is enabled but set to off by default

UseLastlog on

In order to keep log file dates consistent after chroot, use timezone info

from /etc/localtime. If this is not set, and proftpd is configured to

chroot (e.g. DefaultRoot or <Anonymous>), it will use the non-daylight

savings timezone regardless of whether DST is in effect.

SetEnv TZ :/etc/localtime

<IfModule mod_quotatab.c>
QuotaEngine off

<IfModule mod_ratio.c>
Ratios off

Delay engine reduces impact of the so-called Timing Attack described in

It is on by default.

<IfModule mod_delay.c>
DelayEngine on

<IfModule mod_ctrls.c>
ControlsEngine off
ControlsMaxClients 2
ControlsLog /var/log/proftpd/controls.log
ControlsInterval 5
ControlsSocket /var/run/proftpd/proftpd.sock

<IfModule mod_ctrls_admin.c>
AdminControlsEngine off

Alternative authentication frameworks

Include /etc/proftpd/ldap.conf

Include /etc/proftpd/sql.conf

This is used for FTPS connections

Include /etc/proftpd/tls.conf

Useful to keep VirtualHost/VirtualRoot directives separated

Include /etc/proftpd/virtuals.conf

A basic anonymous configuration, no upload directories.

<Anonymous ~ftp>

User ftp

Group nogroup

# We want clients to be able to login with “anonymous” as well as “ftp”

UserAlias anonymous ftp

# Cosmetic changes, all files belongs to ftp user

DirFakeUser on ftp

DirFakeGroup on ftp

RequireValidShell off

# Limit the maximum number of anonymous logins

MaxClients 10

# We want ‘welcome.msg’ displayed at login, and ’.message’ displayed

# in each newly chdired directory.

DisplayLogin welcome.msg

DisplayChdir .message

# Limit WRITE everywhere in the anonymous chroot

<Directory *>

<Limit WRITE>




# Uncomment this if you’re brave.

# <Directory incoming>

# # Umask 022 is a good standard umask to prevent new files and dirs

# # (second parm) from being group and world writable.

# Umask 022 022

# <Limit READ WRITE>

# DenyAll

# </Limit>

# <Limit STOR>

# AllowAll

# </Limit>

# </Directory>


Include other custom configuration files

Include /etc/proftpd/conf.d/

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Submit an Answer
1 answer


Make a backup copy of your current configuration:

cp /etc/proftpd/proftpd.conf /usr/local/src/proftpd.conf

Delete your existing configuration file:

rm /etc/proftpd/proftpd.conf

Then grab the modified version from here, use nano to create a new configuration file, and paste the raw contents of the PasteBin in..

nano /etc/proftpd/proftpd.conf

Save, exit, and restart proftpd:

sudo service proftpd restart

You will need to make sure that each user owns their home directory as well as the directories and files below it.

For example, if we have a user example and a home directory of:


as well as a few directories and files:


You’ll need to make sure example owns from /home/example down. This is done by running:

sudo chown -R example:example /home/example

You’d just need to sub in your actual usernames in place of example.