Questions about vsftpd on Linux servers

Some time ago, I met a guy from niub and helped me solve the PAM-based authentication problem of vsftpd. today I encountered n more problems, such as Access denied. and 403 errors, files cannot be uploaded, and so on. so I had to ask the senior man to leave the game again and help me correct it again. thank you very much for this guy. in a society where the benefit is greater than anything else, we can also analyze N files for this group of cainiao .. this spirit is really admirable.

In view of my own problems, I sorted out a record of the senior and my QQ accounts, and then added the actual operations. finally let me realize it. now I am sharing with you the achievements of this brilliant man.

When the user uploads a file, access 403 or access denied occurs.

Answer: This is mainly a permission issue in the user vsftpd. in the conf file: anon_umask = 022 or anon_umask = 133,022 indicates the 755 permission. 133 indicates the 644 permission, and then grant the permission to the file chmod 644 xx. PHP/chmod 644 name

The user cannot upload the file. The error 550 or 553 is returned.

The user group may be faulty. For example, if your website is accessed by the WWW user, change guest_username = xxx in vsftpd. conf to www.

In addition, I posted my vsftpd configuration file:
CopyCode The Code is as follows: # 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.
#
# Allow Anonymous FTP? (Beware-allowed by default if you comment this out ).
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 CT that (022 is used by most other ftpd's)
Local_umask = 022
#
# 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
#
# The target log file can be vsftpd_log_file or xferlog_file.
# This depends on setting xferlog_std_format Parameter
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
# A different user. Note! Using "root" for uploaded files is not
# Recommended!
# Chown_uploads = Yes
# Chown_username = whoever
#
# The name of log file when xferlog_enable = yes and xferlog_std_format = Yes
# Warning-changing this filename affects/etc/logrotate. d/vsftpd. Log
# Xferlog_file =/var/log/xferlog
#
# Switches between logging into vsftpd_log_file and xferlog_file files.
# No writes to vsftpd_log_file, yes to xferlog_file
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
# Ftp server can use as a totally isolated and unprivileged user.
# Nopriv_user = ft1_cure
#
# Enable this and the server will recognize 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
# 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 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
# Users to not chroot ().
# 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
# 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
#
# When "listen" directive is enabled, vsftpd runs in standalone mode and
# Listens on IPv4 Sockets. This directive cannot be used in Conjunction
# With the listen_ipv6 directive.
Listen = Yes
#
# This Directive enables listening on IPv6 Sockets. To listen on IPv4 and IPv6
# Sockets, you must run two copies of vsftpd whith two configuration files.
# Make sure, that one of the listen options is commented !!
# Listen_ipv6 = Yes
Pam_service_name = vsftpd
<Strong> user_config_dir =/etc/vsftpd/user_config_dir/* used for Pam-based authentication */
Userlist_enable = Yes
Tcp_wrappers = Yes
Guest_enable = Yes
Guest_username = www/* Note here. It is very likely that your user may cause your permission problems */
Local_root =/home/WWW
Anon_umask = 022/* here is the permission issue mentioned above */
</Strong>

if you have used Ram authentication. then you can refer to my individual user configuration. the file is as follows copy Code the code is as follows: anon_world_readable_only = No
write_enable = Yes
anon_upload_enable = Yes
enabled = Yes
local_root =/var/Public
anon_mkdir_write_enable = Yes BR>