Overview

If you want to move files between your desktop and a Linux server using FileZilla and NGINX this guide will save you time and dignity. You will learn how to prepare the server create an FTP account set tight permissions configure passive mode open firewall ports and connect with FileZilla for secure file transfer.

What you need

• Linux server with sudo access
• NGINX serving web content or static files
• FTP daemon such as vsftpd or pure-ftpd
• FileZilla client on your workstation

Prepare the server

Install a lightweight FTP daemon. On Debian or Ubuntu run

apt update && apt install vsftpd -y

Then enable and start the service

systemctl enable --now vsftpd

Keep NGINX in mind if it serves the same directories. Do not make the FTP user the web server user unless you enjoy permission hell.

Create FTP user and set permissions

Create a dedicated account for FTP access. For a simple local user try

adduser ftpuser

Place uploads in a directory owned by the FTP user and readable by NGINX if those files should be served

mkdir -p /var/www/uploads
chown ftpuser /var/www/uploads
chmod 750 /var/www/uploads

Use chroot or virtual users in your FTP daemon config to restrict access to the intended path.

Configure passive mode and firewall

Passive mode matters when clients sit behind NAT or corporate routers. Pick a port range such as 40000 to 50000 and configure those ports in your FTP daemon. Also set the server public address in the passive settings so clients can reach back to you.

Example vsftpd options to edit in the daemon config file

pasv_enable=YES
pasv_min_port=40000
pasv_max_port=50000
pasv_address=your.server.public.ip
ssl_enable=YES

Open TCP port 21 and the passive range on your firewall. With UFW you can allow 21 and then use your firewall tool to allow the passive ports. With firewalld use port range syntax to add the range.

Set up FileZilla client

Open FileZilla and add a new site in the Site Manager. Use the server address your FTP username and password. Choose passive mode in transfer settings and select TLS if your daemon offers FTP over TLS for encrypted transfers. Save the site so you do not retype credentials like a caveman.

• Host field is your server name or IP
• Protocol is FTP
• Encryption use explicit FTP over TLS if available
• Logon type is Normal

Test transfer and common troubleshooting

Upload a small file to the upload directory then check that NGINX serves it if that is the goal. If transfers hang or directory listing fails check these items

• Firewall rules for port 21 and the passive range
• Passive mode settings and the public address in the FTP daemon
• User permissions on the upload directory
• Daemon logs for authentication or connection errors

If TLS fails verify certificates and that the daemon is configured for explicit TLS. If you still have problems enable verbose logging in FileZilla and read the server logs like a detective who drinks too much coffee.

Quick checklist

• Install an FTP daemon such as vsftpd
• Create a dedicated FTP user and set tight permissions
• Configure passive mode and advertise the public IP
• Open port 21 and the passive port range on the firewall
• Use FileZilla with passive mode and TLS for secure file transfer

Summary

You now have a pragmatic path to connect FileZilla to an NGINX hosted file area on a Linux server. The key points are to isolate FTP users set correct server permissions configure passive mode and keep firewall rules in sync. Do that and you will transfer files without drama or mystery.