CentOS 6 VSFTP 553 Could not create file
Clash Royale CLAN TAG#URR8PPP
up vote
4
down vote
favorite
I installed vsftpd yesterday on CentOS 6, however didn't get a chance to test it today. When I went to upload a test file it's coming back and giving me this error:
553 Could not create file
After some quick googling the information I found on resolving the error, including this post were already things I tried...
- Confirm user that is connecting to FTP is a part of the group that owns the directory
- Confirm the
vsftpd.conffile haswrite_enableset totrue
I even went so far as to test changing the group on the whole path down to the destination folder.
EDIT:
Just to expand on this, at the time I did ensure that the modes on the
directories were set appropriately as well.
What I ended up doing was uninstalling vsftpd and re-installing from
yum. After I did this things worked appropriately. So I'm convinced
it was a setting invsftpd.conffile. However I didn't save a copy
of it to do a diff off of to confirm.
Hopefully someone else who has had the same problem with the same
symptoms and found out what the cause was can accurately answer this
question here for someone else who comes along.
centos permissions ftp vsftpd
edited Apr 13 '17 at 12:36
Community♦
1
asked Oct 26 '12 at 20:17
Mike Keller
136116
add a comment |Â
up vote
4
down vote
favorite
I installed vsftpd yesterday on CentOS 6, however didn't get a chance to test it today. When I went to upload a test file it's coming back and giving me this error:
553 Could not create file
After some quick googling the information I found on resolving the error, including this post were already things I tried...
- Confirm user that is connecting to FTP is a part of the group that owns the directory
- Confirm the
vsftpd.conffile haswrite_enableset totrue
I even went so far as to test changing the group on the whole path down to the destination folder.
EDIT:
Just to expand on this, at the time I did ensure that the modes on the
directories were set appropriately as well.
What I ended up doing was uninstalling vsftpd and re-installing from
yum. After I did this things worked appropriately. So I'm convinced
it was a setting invsftpd.conffile. However I didn't save a copy
of it to do a diff off of to confirm.
Hopefully someone else who has had the same problem with the same
symptoms and found out what the cause was can accurately answer this
question here for someone else who comes along.
centos permissions ftp vsftpd
edited Apr 13 '17 at 12:36
Community♦
1
asked Oct 26 '12 at 20:17
Mike Keller
136116
add a comment |Â
up vote
4
down vote
favorite
up vote
4
down vote
favorite
I installed vsftpd yesterday on CentOS 6, however didn't get a chance to test it today. When I went to upload a test file it's coming back and giving me this error:
553 Could not create file
After some quick googling the information I found on resolving the error, including this post were already things I tried...
- Confirm user that is connecting to FTP is a part of the group that owns the directory
- Confirm the
vsftpd.conffile haswrite_enableset totrue
I even went so far as to test changing the group on the whole path down to the destination folder.
EDIT:
Just to expand on this, at the time I did ensure that the modes on the
directories were set appropriately as well.
What I ended up doing was uninstalling vsftpd and re-installing from
yum. After I did this things worked appropriately. So I'm convinced
it was a setting invsftpd.conffile. However I didn't save a copy
of it to do a diff off of to confirm.
Hopefully someone else who has had the same problem with the same
symptoms and found out what the cause was can accurately answer this
question here for someone else who comes along.
centos permissions ftp vsftpd
edited Apr 13 '17 at 12:36
Community♦
1
asked Oct 26 '12 at 20:17
Mike Keller
136116
I installed vsftpd yesterday on CentOS 6, however didn't get a chance to test it today. When I went to upload a test file it's coming back and giving me this error:
553 Could not create file
After some quick googling the information I found on resolving the error, including this post were already things I tried...
- Confirm user that is connecting to FTP is a part of the group that owns the directory
- Confirm the
vsftpd.conffile haswrite_enableset totrue
I even went so far as to test changing the group on the whole path down to the destination folder.
EDIT:
Just to expand on this, at the time I did ensure that the modes on the
directories were set appropriately as well.
What I ended up doing was uninstalling vsftpd and re-installing from
yum. After I did this things worked appropriately. So I'm convinced
it was a setting invsftpd.conffile. However I didn't save a copy
of it to do a diff off of to confirm.
Hopefully someone else who has had the same problem with the same
symptoms and found out what the cause was can accurately answer this
question here for someone else who comes along.
centos permissions ftp vsftpd
centos permissions ftp vsftpd
edited Apr 13 '17 at 12:36
Community♦
1
asked Oct 26 '12 at 20:17
Mike Keller
136116
edited Apr 13 '17 at 12:36
Community♦
1
asked Oct 26 '12 at 20:17
Mike Keller
136116
edited Apr 13 '17 at 12:36
Community♦
1
edited Apr 13 '17 at 12:36
Community♦
1
edited Apr 13 '17 at 12:36
Community♦
1
1
asked Oct 26 '12 at 20:17
Mike Keller
136116
asked Oct 26 '12 at 20:17
Mike Keller
136116
asked Oct 26 '12 at 20:17
Mike Keller
136116
136116
add a comment |Â
add a comment |Â
4 Answers
4
active
oldest
votes
up vote
4
down vote
That group should have rwx permissions on that folder. If not run
chmod 775 <directory>
answered Nov 7 '12 at 20:05
Laurentiu Roescu
50936
While technically correct, and I should edit the original question to highlight this, this did not resolve the issue at the time either. What I ended up doing was uninstalling vsftpd, and reinstalling through yum again. After that everything worked appropriately. Leading me to believe that the issue was in the conf file somewhere. However I unfortunately didn't save the original vsftpd.conf to do a diff between the two.
– Mike Keller
Nov 8 '12 at 4:05
add a comment |Â
up vote
2
down vote
You need to run the following commands to allow in SELinux upload and edit files:
setsebool -P allow_ftpd_full_access on
setsebool -P ftp_home_dir on
answered Jun 10 '14 at 4:37
VictorV
1211
Did the trick for me. However, it'stftp_home_dirby now.
– BurninLeo
Jan 16 at 12:54
add a comment |Â
up vote
0
down vote
in the ftp root dir
setsebool -P tftp_home_dir on
setsebool -P ftpd_full_access on
did work for me
answered Aug 31 at 15:24
kadir malak
1
add a comment |Â
up vote
-1
down vote
setsebool -P ftpd_full_access 1
edited Sep 6 '16 at 9:38
Anthon
58.9k1796160
answered Sep 6 '16 at 7:34
Tawan
1
2
Can you please extend you answer. One line answer with just a command is not counted as helpful
– Romeo Ninov
Sep 6 '16 at 7:55
add a comment |Â
4 Answers
4
active
oldest
votes
4 Answers
4
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
4
down vote
That group should have rwx permissions on that folder. If not run
chmod 775 <directory>
answered Nov 7 '12 at 20:05
Laurentiu Roescu
50936
While technically correct, and I should edit the original question to highlight this, this did not resolve the issue at the time either. What I ended up doing was uninstalling vsftpd, and reinstalling through yum again. After that everything worked appropriately. Leading me to believe that the issue was in the conf file somewhere. However I unfortunately didn't save the original vsftpd.conf to do a diff between the two.
– Mike Keller
Nov 8 '12 at 4:05
add a comment |Â
up vote
4
down vote
That group should have rwx permissions on that folder. If not run
chmod 775 <directory>
answered Nov 7 '12 at 20:05
Laurentiu Roescu
50936
While technically correct, and I should edit the original question to highlight this, this did not resolve the issue at the time either. What I ended up doing was uninstalling vsftpd, and reinstalling through yum again. After that everything worked appropriately. Leading me to believe that the issue was in the conf file somewhere. However I unfortunately didn't save the original vsftpd.conf to do a diff between the two.
– Mike Keller
Nov 8 '12 at 4:05
add a comment |Â
up vote
4
down vote
up vote
4
down vote
That group should have rwx permissions on that folder. If not run
chmod 775 <directory>
answered Nov 7 '12 at 20:05
Laurentiu Roescu
50936
That group should have rwx permissions on that folder. If not run
chmod 775 <directory>
answered Nov 7 '12 at 20:05
Laurentiu Roescu
50936
answered Nov 7 '12 at 20:05
Laurentiu Roescu
50936
answered Nov 7 '12 at 20:05
Laurentiu Roescu
50936
answered Nov 7 '12 at 20:05
Laurentiu Roescu
50936
50936
While technically correct, and I should edit the original question to highlight this, this did not resolve the issue at the time either. What I ended up doing was uninstalling vsftpd, and reinstalling through yum again. After that everything worked appropriately. Leading me to believe that the issue was in the conf file somewhere. However I unfortunately didn't save the original vsftpd.conf to do a diff between the two.
– Mike Keller
Nov 8 '12 at 4:05
add a comment |Â
While technically correct, and I should edit the original question to highlight this, this did not resolve the issue at the time either. What I ended up doing was uninstalling vsftpd, and reinstalling through yum again. After that everything worked appropriately. Leading me to believe that the issue was in the conf file somewhere. However I unfortunately didn't save the original vsftpd.conf to do a diff between the two.
– Mike Keller
Nov 8 '12 at 4:05
While technically correct, and I should edit the original question to highlight this, this did not resolve the issue at the time either. What I ended up doing was uninstalling vsftpd, and reinstalling through yum again. After that everything worked appropriately. Leading me to believe that the issue was in the conf file somewhere. However I unfortunately didn't save the original vsftpd.conf to do a diff between the two.
– Mike Keller
Nov 8 '12 at 4:05
While technically correct, and I should edit the original question to highlight this, this did not resolve the issue at the time either. What I ended up doing was uninstalling vsftpd, and reinstalling through yum again. After that everything worked appropriately. Leading me to believe that the issue was in the conf file somewhere. However I unfortunately didn't save the original vsftpd.conf to do a diff between the two.
– Mike Keller
Nov 8 '12 at 4:05
add a comment |Â
up vote
2
down vote
You need to run the following commands to allow in SELinux upload and edit files:
setsebool -P allow_ftpd_full_access on
setsebool -P ftp_home_dir on
answered Jun 10 '14 at 4:37
VictorV
1211
Did the trick for me. However, it'stftp_home_dirby now.
– BurninLeo
Jan 16 at 12:54
add a comment |Â
up vote
2
down vote
You need to run the following commands to allow in SELinux upload and edit files:
setsebool -P allow_ftpd_full_access on
setsebool -P ftp_home_dir on
answered Jun 10 '14 at 4:37
VictorV
1211
Did the trick for me. However, it'stftp_home_dirby now.
– BurninLeo
Jan 16 at 12:54
add a comment |Â
up vote
2
down vote
up vote
2
down vote
You need to run the following commands to allow in SELinux upload and edit files:
setsebool -P allow_ftpd_full_access on
setsebool -P ftp_home_dir on
answered Jun 10 '14 at 4:37
VictorV
1211
You need to run the following commands to allow in SELinux upload and edit files:
setsebool -P allow_ftpd_full_access on
setsebool -P ftp_home_dir on
answered Jun 10 '14 at 4:37
VictorV
1211
answered Jun 10 '14 at 4:37
VictorV
1211
answered Jun 10 '14 at 4:37
VictorV
1211
answered Jun 10 '14 at 4:37
VictorV
1211
1211
Did the trick for me. However, it'stftp_home_dirby now.
– BurninLeo
Jan 16 at 12:54
add a comment |Â
Did the trick for me. However, it'stftp_home_dirby now.
– BurninLeo
Jan 16 at 12:54
Did the trick for me. However, it's
tftp_home_dir by now.– BurninLeo
Jan 16 at 12:54
Did the trick for me. However, it's
tftp_home_dir by now.– BurninLeo
Jan 16 at 12:54
add a comment |Â
up vote
0
down vote
in the ftp root dir
setsebool -P tftp_home_dir on
setsebool -P ftpd_full_access on
did work for me
answered Aug 31 at 15:24
kadir malak
1
add a comment |Â
up vote
0
down vote
in the ftp root dir
setsebool -P tftp_home_dir on
setsebool -P ftpd_full_access on
did work for me
answered Aug 31 at 15:24
kadir malak
1
add a comment |Â
up vote
0
down vote
up vote
0
down vote
in the ftp root dir
setsebool -P tftp_home_dir on
setsebool -P ftpd_full_access on
did work for me
answered Aug 31 at 15:24
kadir malak
1
in the ftp root dir
setsebool -P tftp_home_dir on
setsebool -P ftpd_full_access on
did work for me
answered Aug 31 at 15:24
kadir malak
1
answered Aug 31 at 15:24
kadir malak
1
answered Aug 31 at 15:24
kadir malak
1
answered Aug 31 at 15:24
kadir malak
1
1
add a comment |Â
add a comment |Â
up vote
-1
down vote
setsebool -P ftpd_full_access 1
edited Sep 6 '16 at 9:38
Anthon
58.9k1796160
answered Sep 6 '16 at 7:34
Tawan
1
2
Can you please extend you answer. One line answer with just a command is not counted as helpful
– Romeo Ninov
Sep 6 '16 at 7:55
add a comment |Â
up vote
-1
down vote
setsebool -P ftpd_full_access 1
edited Sep 6 '16 at 9:38
Anthon
58.9k1796160
answered Sep 6 '16 at 7:34
Tawan
1
2
Can you please extend you answer. One line answer with just a command is not counted as helpful
– Romeo Ninov
Sep 6 '16 at 7:55
add a comment |Â
up vote
-1
down vote
up vote
-1
down vote
setsebool -P ftpd_full_access 1
edited Sep 6 '16 at 9:38
Anthon
58.9k1796160
answered Sep 6 '16 at 7:34
Tawan
1
setsebool -P ftpd_full_access 1
edited Sep 6 '16 at 9:38
Anthon
58.9k1796160
answered Sep 6 '16 at 7:34
Tawan
1
edited Sep 6 '16 at 9:38
Anthon
58.9k1796160
edited Sep 6 '16 at 9:38
Anthon
58.9k1796160
edited Sep 6 '16 at 9:38
Anthon
58.9k1796160
58.9k1796160
answered Sep 6 '16 at 7:34
Tawan
1
answered Sep 6 '16 at 7:34
Tawan
1
answered Sep 6 '16 at 7:34
Tawan
1
1
2
Can you please extend you answer. One line answer with just a command is not counted as helpful
– Romeo Ninov
Sep 6 '16 at 7:55
add a comment |Â
2
Can you please extend you answer. One line answer with just a command is not counted as helpful
– Romeo Ninov
Sep 6 '16 at 7:55
2
2
Can you please extend you answer. One line answer with just a command is not counted as helpful
– Romeo Ninov
Sep 6 '16 at 7:55
Can you please extend you answer. One line answer with just a command is not counted as helpful
– Romeo Ninov
Sep 6 '16 at 7:55
add a comment |Â
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f53003%2fcentos-6-vsftp-553-could-not-create-file%23new-answer', 'question_page');
);
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
