anonymous ftp doesn't work with secure_access_group

Version 1.41

Bugfix
Finished

It appears as though proftpd is running as "ftp" when doing the chdir/chroot, prior to dropping the privileges to that of the user. This caused an error for the anonymous ftp account, as mentioned below. The fix is to add "ftp" to the "access" group, eg: usermod -G access ftp and then restart proftpd. For any new systems where the access group does not yet exist, the ftp value will be added to the access group autmatically. Error: Apr 2 23:29:43 server proftpd[12843]: 192.168.0.2 (127.0.0.1[127.0.0.1]) - FTP session opened. Apr 2 23:29:47 server proftpd[12843]: 192.168.0.2 (127.0.0.1[127.0.0.1]) - notice: unable to use '~/' [resolved to '/home/testuser/domains/testdomain.com/public_ftp/']: Permission denied Apr 2 22:29:47 server proftpd[12843]: 192.168.0.2 (127.0.0.1[127.0.0.1]) - Preparing to chroot to directory '~/' Apr 2 22:29:47 server proftpd[12843]: 192.168.0.2 (127.0.0.1[127.0.0.1]) - chroot to '~/' failed for user 'anonymous@testdomain.com': Operation not permitted Apr 2 22:29:47 server proftpd[12843]: 192.168.0.2 (127.0.0.1[127.0.0.1]) - error: unable to set default root directory Apr 2 22:29:47 server proftpd[12843]: 192.168.0.2 (127.0.0.1[127.0.0.1]) - FTP session closed.

Interested to try DirectAdmin? Get a 30-day Free Trial!