550 ошибка ftp linux

Какой же web сервер без ftp. Для нашего сервера мы будем использовать vsftpd — простой, быстрый и безопасный FTP сервер, который будет доступен из мира (пробросим порты на роутере).
Установка сервера предельно проста:

sudo apt-get install vsftpd

После установки необходимо немного настроить наш сервер. Для подключения к ftp серверу используеться профиль пользователя системы. Настройка сервера производится через конфигурационный файл /etc/vsftpd.conf, откроем его и немного отредактируем. Выполним команду:

sudo nano /etc/vsftpd.conf

Не будем описывать все параметры, остановимся на самых интересных:

listen=YES
anonymous_enable=NO разрешим вход только локальным пользователям
local_enable=YES
write_enable=YES разрешим пользователям записывать файлы
local_umask=022 укажем серверу автоматически выставлять нужные права (755 на папки и 644 на файлы)

После всех манипуляций не забываем перезагрузить сервер:

sudo service vsftpd restart

После всех манипуляций не забываем перезагрузить сервер:

sudo service vsftpd restart

550 Permission denied при попытке записать файлы

Сервер настроен, подключение есть, но когда мы пытаемся скопировать что то на наш сервер ничего не выходит. Получаем ошибку «550 Permission denied«.
В первую очередь необходимо убедится, что в конфигурационном файле /etc/vsftpd.conf присутствует строчка write_enable=YES.
Пользователям разрешена запись файлов но ничего не происходит и мы все так же получаем 550 Permission denied.
Дело в том что у папки в которую вы хотите записать файлы должны быть соответствующие права доступа, а именно 777. Выполним команду:

sudo chmod -R 777 /my_ftp_dir/

Показывать скрытые файлы при подключение

Настроили, подключаемся — все хорошо, да не очень. Не видны скрытые файлы и папки. Для того что бы скрытые файлы стали видимыми в конфигурационном файле /etc/vsftpd.conf допишем следующею строку:

force_dot_files=YES

После всех манипуляций не забываем перезагрузить сервер:

sudo service vsftpd restart

FTP is a simple method to upload files to the server.

Although, it is rather easy to transfer files, FTP users often get stuck with errors. One such FTP error is “550 No such file or directory“.

Broadly speaking, this error means that the file or folder do not exist.

As part of our Outsourced Technical Support Services, we regularly fix these type of FTP errors for our customers.

Today, we’ll see the causes for the error “FTP 550 no such file or directory” and how our Support Engineers fix them.

What is FTP 550 error?

Firstly, let’s get a quick idea on the FTP 550 error.

The 5xx error falls under the permanent negative completion reply status of the FTP server. And, it means that the FTP server did not accept the command and the requested action did not take place. Further more, x5x error denotes File system errors in FTP server.
Overall, the 550 error means the file was not found or there are access restrictions for the file.

Causes for “FTP 550 no such file or directory”

Recently, one of our customers reported trouble with FTP upload. The logs of his FTP session looked as shown below.

STATUS:> Transferring file "/mydir/home.html"...
COMMAND:> SIZE home.html
550 home.html: No such file.
STATUS:> Requested action not taken (e.g., file or directory not found, no access).
COMMAND:> CWD /mydir/home.html
550 /mydir/home.html: No such file or directory.

Here, the customer was trying to PUT the file home.html via FTP. And that resulted in the error.

Now, let’s see the top causes for the error.

1. Incorrect path

Usually, “FTP 550 no such file or directory” error happens when the customers try to upload files from the wrong directory.

For example, when the file is present in the folder /home/user/abc.html, an attempt to upload from the path /home will cause this error.

This error also happens when customer uses the relative path in FTP.

2. Permission problems

Similarly, wrong permission on the files or folders can also cause this 550 error. When the user do not have privileges on the file they are trying to access, it will report the 550 error.

Additionally, a typo in the file name will also lead to this error.

3. Wrong Mount points

Again, we often see FTP 550 errors when users trying to access files in the mounted file systems.

For instance, recently a customer complained about the problems accessing files via FTP. In his server, he had a mounted file system. But, this mount failed after a server reboot. And, when he tried to access a file in this mounted directory, it resulted in the error:

550 : No such file or directory

How to fix FTP 550 error?

Till now, we saw the various causes for the FTP 550 error. Let’s now have a look on how to fix it.

We already know that the underlying reason for the FTP 550 error could be file not residing at the path.

That’s why, our Support Engineers first check the exact path that the customer uses via FTP. We connect to the server via SSH and confirm the presence of the file. If the file is not found on the path, we advise customer on the correct path. Or, for file name typo issues, we educate customer on the exact file name.

We always encourage customers to use the absolute path of the file in FTP connections.

Similarly, we check the server mount points and confirm the availability of file system and its contents too.

[Are you getting 550 error while accessing files via FTP?  We can quickly fix it for you.]

Conclusion

In short, FTP error “550 no such file or directory” happens mainly when the file do not exist at the path, due to permission problems, etc. Today, we saw the top causes for the error and how our Support Engineers fix them.

var google_conversion_label = «owonCMyG5nEQ0aD71QM»;

Всем доброго времени суток.
Ftp+mysql+php ставил  вот по этому мануалу http://sudouser.com/ustanovka-i-nastrojka-vsftpd-mysql-ubuntu-debian

в итоге авторизацию прохожу чтение есть а вот запись и создание папок не могу  пишет
550: Create directory operation failed.

в чем проблема понять не  могу 

#
#vsftpd.conf
#
listen=YES
anonymous_enable=YES
local_enable=YES
write_enable=YES
local_umask=022
dirmessage_enable=YES
xferlog_enable=YES
connect_from_port_20=YES
nopriv_user=vsftpd
chroot_local_user=YES
secure_chroot_dir=/var/run/vsftpd
pam_service_name=vsftpd
rsa_cert_file=/etc/ssl/certs/vsftpd.pem
guest_enable=YES
guest_username=vsftpd
local_root=/home/vsftpd/$USER
user_sub_token=$USER
virtual_use_local_privs=YES
user_config_dir=/etc/vsftpd_user_conf

Логи

Tue Jul  8 11:56:00 2014 [pid 1] [kirill] OK LOGIN: Client «192.168.0.4»
Tue Jul  8 11:56:10 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 11:56:17 2014 [pid 1] [kirill] OK LOGIN: Client «192.168.0.4»
Tue Jul  8 11:56:22 2014 [pid 4] [kirill] FAIL MKDIR: Client «192.168.0.4», «/1/1»
Tue Jul  8 12:03:40 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 12:03:40 2014 [pid 1] [kirill] OK LOGIN: Client «192.168.0.4»
Tue Jul  8 12:03:47 2014 [pid 4] [kirill] FAIL MKDIR: Client «192.168.0.4», «/11»
Tue Jul  8 12:15:26 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 12:15:26 2014 [pid 1] [kirill] OK LOGIN: Client «192.168.0.4»
Tue Jul  8 12:15:37 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 12:15:44 2014 [pid 1] [kirill] OK LOGIN: Client «192.168.0.4»
Tue Jul  8 12:15:51 2014 [pid 4] [kirill] OK DOWNLOAD: Client «192.168.0.4», «/vsftpd.conf», 443 bytes, 46.49Kbyte/sec
Tue Jul  8 12:16:40 2014 [pid 4] [kirill] OK DOWNLOAD: Client «192.168.0.4», «/vsftpd.conf», 443 bytes, 26.94Kbyte/sec
Tue Jul  8 12:23:41 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 12:23:47 2014 [pid 1] [kirill] OK LOGIN: Client «192.168.0.4»
Tue Jul  8 12:23:56 2014 [pid 4] [kirill] FAIL MKDIR: Client «192.168.0.4», «/tru»

Tue Jul  8 11:07:02 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 11:07:09 2014 [pid 1] [kk] OK LOGIN: Client «192.168.0.4»
Tue Jul  8 11:07:16 2014 [pid 4] [kk] FAIL MKDIR: Client «192.168.0.4», «/1»
Tue Jul  8 11:10:11 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 11:10:11 2014 [pid 1] [ftp] OK LOGIN: Client «192.168.0.4», anon password «kk»
Tue Jul  8 11:43:38 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 11:43:49 2014 [pid 1] [kirill] FAIL LOGIN: Client «192.168.0.4»
Tue Jul  8 11:43:56 2014 [pid 1] [kk] OK LOGIN: Client «192.168.0.4»
Tue Jul  8 11:43:59 2014 [pid 5] [kk] FAIL MKDIR: Client «192.168.0.4», «/1»
Tue Jul  8 11:47:27 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 11:47:35 2014 [pid 1] [kirill] OK LOGIN: Client «192.168.0.4»
Tue Jul  8 11:47:39 2014 [pid 4] [kirill] FAIL MKDIR: Client «192.168.0.4», «/1»
Tue Jul  8 11:48:39 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 11:48:45 2014 [pid 1] [kirill] OK LOGIN: Client «192.168.0.4»
Tue Jul  8 11:48:49 2014 [pid 4] [kirill] FAIL MKDIR: Client «192.168.0.4», «/asdf»
Tue Jul  8 11:56:00 2014 [pid 2] CONNECT: Client «192.168.0.4»
Tue Jul  8 11:56:00 2014 [pid 1] [kirill] OK LOGIN: Client «192.168.0.4»

Moderator: Project members

Поставил proftpd с webmin на вдс с Ubuntu 14.04
Создал аккаунт,подключаюсь,хочу отредактировать файл.
Выдает:
Команда: PASV
Ответ: 227 Entering Passive Mode (188,188,42,133,195,55).
Команда: STOR access.log
Ответ: 550 access.log: Permission denied
Ошибка: Критическая ошибка при передаче файлов

Сделал выводы,что проблемы с правами. Присвоил всем папкам права для ftp пользователя т.е.
chown -R ftpuser:ftpuser *

Да,в этом случаи по ftp все файлы записывает,но битрикс или вордпресс отказываются работать корректно,т.к. сами не могу записывать файлы,элементарно загрузить медифайл или установить плагин не удастся.

Как решить данную проблему?

Hi Guys,

again with problem about LAMP, now I am trying to setup the LAMP in another way, but I am having issues with VSFTP, I am unable to write but I don’t understand why. I configured my local user to write but this configuration seems to not work properly.

I have to write inside: /var/www/html as default directory by Apache2.

I gave these owners and these permissions to these folders:

ls -l /var/www
total 4
drwxr-xr-x 2 root www-data 4096 May 21 00:51 html

I added my user to FTP group and the WWW-DATA:

webby@web-server:~$ groups
webby cdrom floppy audio dip www-data video plugdev netdev bluetooth ftp

I am using this configuration:

# Example config file /etc/vsftpd.conf
#
# The default compiled in settings are fairly paranoid. This sample file
# loosens things up a bit, to make the ftp daemon more usable.
# Please see vsftpd.conf.5 for all compiled in defaults.
#
# READ THIS: This example file is NOT an exhaustive list of vsftpd options.
# Please read the vsftpd.conf.5 manual page to get a full idea of vsftpd's
# capabilities.
#
#
# Run standalone?  vsftpd can run either from an inetd or as a standalone
# daemon started from an initscript.
listen=NO
#
# This directive enables listening on IPv6 sockets. By default, listening
# on the IPv6 "any" address (::) will accept connections from both IPv6
# and IPv4 clients. It is not necessary to listen on *both* IPv4 and IPv6
# sockets. If you want that (perhaps because you want to listen on specific
# addresses) then you must run two copies of vsftpd with two configuration
# files.
listen_ipv6=YES
#
# Allow anonymous FTP? (Disabled by default).
anonymous_enable=NO
#
# Uncomment this to allow local users to log in.
local_enable=YES
#
# Uncomment this to enable any form of FTP write command.
write_enable=YES
#
# Default umask for local users is 077. You may wish to change this to 022,
# if your users expect that (022 is used by most other ftpd's)
#local_umask=022
local_root=/var/www/html/
#
# Uncomment this to allow the anonymous FTP user to upload files. This only
# has an effect if the above global write enable is activated. Also, you will
# obviously need to create a directory writable by the FTP user.
#anon_upload_enable=YES
#
# Uncomment this if you want the anonymous FTP user to be able to create
# new directories.
#anon_mkdir_write_enable=YES
#
# Activate directory messages - messages given to remote users when they
# go into a certain directory.
dirmessage_enable=YES
#
# If enabled, vsftpd will display directory listings with the time
# in  your  local  time  zone.  The default is to display GMT. The
# times returned by the MDTM FTP command are also affected by this
# option.
use_localtime=YES
#
# Activate logging of uploads/downloads.
xferlog_enable=YES
#
# Make sure PORT transfer connections originate from port 20 (ftp-data).
connect_from_port_20=YES
#
# If you want, you can arrange for uploaded anonymous files to be owned by
# a different user. Note! Using "root" for uploaded files is not
# recommended!
#chown_uploads=YES
#chown_username=whoever
#
# You may override where the log file goes if you like. The default is shown
# below.
#xferlog_file=/var/log/vsftpd.log
#
# If you want, you can have your log file in standard ftpd xferlog format.
# Note that the default log file location is /var/log/xferlog in this case.
#xferlog_std_format=YES
#
# You may change the default value for timing out an idle session.
#idle_session_timeout=600
#
# You may change the default value for timing out a data connection.
#data_connection_timeout=120
#
# It is recommended that you define on your system a unique user which the
# ftp server can use as a totally isolated and unprivileged user.
#nopriv_user=ftpsecure
#
# Enable this and the server will recognise asynchronous ABOR requests. Not
# recommended for security (the code is non-trivial). Not enabling it,
# however, may confuse older FTP clients.
#async_abor_enable=YES
#
# By default the server will pretend to allow ASCII mode but in fact ignore
# the request. Turn on the below options to have the server actually do ASCII
# mangling on files when in ASCII mode.
# Beware that on some FTP servers, ASCII support allows a denial of service
# attack (DoS) via the command "SIZE /big/file" in ASCII mode. vsftpd
# predicted this attack and has always been safe, reporting the size of the
# raw file.
# ASCII mangling is a horrible feature of the protocol.
#ascii_upload_enable=YES
#ascii_download_enable=YES
#
# You may fully customise the login banner string:
#ftpd_banner=Welcome to blah FTP service.
#
# You may specify a file of disallowed anonymous e-mail addresses. Apparently
# useful for combatting certain DoS attacks.
#deny_email_enable=YES
# (default follows)
#banned_email_file=/etc/vsftpd.banned_emails
#
# You may restrict local users to their home directories.  See the FAQ for
# the possible risks in this before using chroot_local_user or
# chroot_list_enable below.
#chroot_local_user=YES
#
# You may specify an explicit list of local users to chroot() to their home
# directory. If chroot_local_user is YES, then this list becomes a list of
# users to NOT chroot().
# (Warning! chroot'ing can be very dangerous. If using chroot, make sure that
# the user does not have write access to the top level directory within the
# chroot)
#chroot_local_user=NO
#chroot_list_enable=YES
# (default follows)
#chroot_list_file=/etc/vsftpd.chroot_list
#
# You may activate the "-R" option to the builtin ls. This is disabled by
# default to avoid remote users being able to cause excessive I/O on large
# sites. However, some broken FTP clients such as "ncftp" and "mirror" assume
# the presence of the "-R" option, so there is a strong case for enabling it.
#ls_recurse_enable=YES
#
# Customization
#
# Some of vsftpd's settings don't fit the filesystem layout by
# default.
#
# This option should be the name of a directory which is empty.  Also, the
# directory should not be writable by the ftp user. This directory is used
# as a secure chroot() jail at times vsftpd does not require filesystem
# access.
secure_chroot_dir=/var/run/vsftpd/empty
#
# This string is the name of the PAM service vsftpd will use.
pam_service_name=vsftpd
#
# This option specifies the location of the RSA certificate to use for SSL
# encrypted connections.
rsa_cert_file=/etc/ssl/certs/ssl-cert-snakeoil.pem
rsa_private_key_file=/etc/ssl/private/ssl-cert-snakeoil.key
ssl_enable=NO

When I tried to setup manually the writing permissions I received this error form ftp console, «I was using chroot_local_user=YES»:

ftp localhost
Connected to localhost.
220 (vsFTPd 3.0.2)
Name (localhost:webby): webby
331 Please specify the password.
Password:
500 OOPS: vsftpd: refusing to run with writable root inside chroot()
Login failed.
421 Service not available, remote server has closed connection

Any idea to solve this? Thanks