I'm setting up vsftpd (2.0.3, FC4) with virtual users. When a user logs in, he should be able to upload files to /ftp, but when I try I'm not able to create/upload files, and I get an "553 Could not create file" error message. I can browse directories and delete files without any problems.

I've printed some info about my basic config, and I hope that you guys will be able to help me...

/Stc



vsftpd.conf:
anonymous_enable=YES
local_enable=YES
write_enable=YES
local_umask=022
anon_umask=077
anon_upload_enable=YES
anon_mkdir_write_enable=YES
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
chown_uploads=YES
chown_username=ftp
xferlog_std_format=YES
pam_service_name=ftp
listen=YES
tcp_wrappers=YES
guest_enable=YES
guest_username=ftp
local_root=/ftp
anon_other_write_enable=YES
chroot_local_user=YES
virtual_use_local_privs=YES



[root@nordsign /]# ls -al
total 242
drwxr-xr-x 30 root root 4096 Oct 19 16:23 .
drwxr-xr-x 30 root root 4096 Oct 19 16:23 ..
(...)
drwxrwxrwx 3 ftp web 4096 Oct 20 10:40 ftp
(...)




Macintosh:~ steffentchr$ ftp ftp.dummy.com
Connected to ftp.dummy.com.
220 (vsFTPd 2.0.3)
Name (ftp.dummy.com):steffentchr): steffen
331 Please specify the password.
Password:
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
226 Directory send OK.
ftp> put Desktop/stc1
local: Desktop/stc1 remote: Desktop/stc1
229 Entering Extended Passive Mode (|||64727|)
553 Could not create file.

hi,

your users "steffen" ..what's her primary and secondary group ?

if you create a file on '/ftp' , users "steffen" can retrieve ? and read it ? or not ?

There's no "steffen" user; along with loads of others it a virtual user mapping against a pam db. As I understand permissions should be based on the ftp-user (guest_username)?

Thanks,
/Stc

I was experiencing the same error. It turned out that a file of the same name already existed in the upload directory.

After deleting the same named file from the upload directory, I got "226 File receive OK."

I solve problem with granting ownership to directory. Command was chown -R webadmin2 /var/www/html.

chown -R webadmin2 /var/www/html works beautifully....
Response: 226 Directory send OK.

1 members found this post helpful.

with this setting you are trying to log in using anonymous user

so you should know that by default anonymous user is not allowed to login on any directory having write permission
so you default login directory inside

should not have write access

once our anonymous user logs in then he will not be able to create any file or directory
so for this reason create a directory inside pub with full permission

or make sure to give relevant permission as per your use with write permission enabled

so once the anonymous user logs in

2 members found this post helpful.

chown -R webadmin2 /var/www/html works beautifully here also
Response: 226 Directory send OK.

Second that, works perfectly.