This article covers a version of CentOS that is no longer supported. If you are currently operating a server running CentOS 6, we highly recommend upgrading or migrating to a supported version of CentOS.
Reason: CentOS 6 reached end of life (EOL) on November 30th, 2020 and no longer receives security patches or updates. For this reason, this guide is no longer maintained.
See Instead:
This guide might still be useful as a reference, but may not work on other CentOS releases. If available, we strongly recommend using a guide written for the version of CentOS you are using.
Warning: FTP is inherently insecure. If you must use FTP, consider securing your FTP connection with SSL/TLS. Otherwise, it is best to use SFTP, a secure alternative to FTP.
The first two letters of vsftpd stand for "very secure" and the program was built to have strongest protection against possible FTP vulnerabilities.
You can quickly install vsftpd on your virtual private server in the command line:
sudo yum install vsftpd
We also need to install the FTP client, so that we can connect to an FTP server:
sudo yum install ftp
Once the files finish downloading, vsftpd will be on your VPS. Generally speaking, the virtual private server is already configured with a reasonable amount of security. However, it does provide access to anonymous users.
Once VSFTP is installed, you can adjust the configuration.
Open up the configuration file:
sudo vi /etc/vsftpd/vsftpd.conf
One primary change you need to make is to change the Anonymous_enable to No:
anonymous_enable=NO
Prior to this change, vsftpd allowed anonymous, unidentified users to access the VPS's files. This is useful if you are seeking to distribute information widely, but may be considered a serious security issue in most other cases. After that, uncomment the local_enable option, changing it to yes.
local_enable=YES
Finish up by uncommenting command to chroot_local_user. When this line is set to Yes, all the local users will be jailed within their chroot and will be denied access to any other part of the server.
chroot_local_user=YES
Finish up by restarting vsftpd:
sudo service vsftpd restart
In order to ensure that vsftpd runs at boot, run chkconfig:
chkconfig vsftpd on
Once you have installed the FTP server and configured it to your liking, you can now access it.
You can reach an FTP server in the browser by typing the domain name into the address bar and logging in with the appropriate ID. Keep in mind, you will only be able to access the user's home directory.
ftp://example.com
Alternatively, you can reach the FTP server through the command line by typing:
ftp example.com
Then you can use the word, "exit," to get out of the FTP shell.
Thanks for learning with the DigitalOcean Community. Check out our offerings for compute, storage, networking, and managed databases.
This textbox defaults to using Markdown to format your answer.
You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!
You may want to add “chkconfig vsftpd on” to the end, otherwise when the server/VPS is rebooted, no user will be able to log-in until vsftpd is started from CLI.
Thanks for the addition—I have updated the article to include chkconfig!
Nice Tutorial! But please add how to setup users and their default path or directory of access.
Hi Sudsachin, that’s a great suggestion! I will build out the article further in the coming days. Thanks!
Etel,
I’m really liking digital ocean tutorials.
I was hoping you could create a tutorial on how to install virtualization and get it started via CentOS 6.3
Can you save me? :)
If you are running virtualization inside of a virtual server from DigitalOcean you will most likely not be able to bridge the connection because the server is already virtualized and running through the hypervisor.
Or is this on a dedicated system.
This is on a dedicated server… I only came across this place via google.
You should be able to get a dedicated server to be setup as a hypervisor with KVM installed on it - however the networking bridge can also be affected on your network setup from the switch that your server is connected to.
Best thing to do is contact your dedicated server provider and see if they can provide you a bit of guidance in getting this setup.
what will be the ftp username and password for this setup?
It will be your existing server user