FileZilla

FileZilla Server Setup and Usage (Windows VDS)

Set up FTP/FTPS on a Windows Server VDS with FileZilla Server. User management, shared folders, SSL, and firewall configuration.

KavesNET Team March 5, 2026 3 min read

Need an FTP server on your Windows VDS for file sharing? FileZilla Server is open source, free, and one of the easiest options to deploy. This guide covers download, user creation, SSL/TLS, and firewall setup.

FileZilla Server vs Client

FileZilla Server: install on the server — others connect to you
FileZilla Client: install on your PC — to connect to other FTP servers

This guide is the server side.

Installation

https://filezilla-project.org/download.php?type=server → download FileZilla Server for Windows
Run setup → Standard install (defaults)
Service mode → “Install as service, started with Windows” ✓
Admin port: 14148 (default), localhost only ✓
Set an admin password (for the management UI)

The FileZilla Server admin opens automatically when done.

Initial configuration

1. Server settings

Server → Configure...:

Listeners: 0.0.0.0:21 (FTP), 0.0.0.0:990 (FTPS — later)
Passive mode ports: 50000-51000 (this range must be open in firewall)
Maximum connections per IP: 10 (DDoS guard)

Create a user

Server → Users → Add:

Username: companymail (one per customer)
Password: strong
Mount points (shared folder):
- Virtual path: /
- Native path: D:\FTP\companymail (create the folder first)
- Permissions: Read, Write, Append, Delete (as needed)

For multiple users, use a Group and apply common settings.

Firewall configuration

Allow inbound on Windows Firewall:

# FTP control port
New-NetFirewallRule -DisplayName "FTP" -Direction Inbound -LocalPort 21 -Protocol TCP -Action Allow

# Passive mode ports
New-NetFirewallRule -DisplayName "FTP Passive" -Direction Inbound -LocalPort 50000-51000 -Protocol TCP -Action Allow

# FTPS (if added)
New-NetFirewallRule -DisplayName "FTPS" -Direction Inbound -LocalPort 990 -Protocol TCP -Action Allow

Make sure these are also open in the KavesNET network firewall.

FTPS (SSL/TLS) — mandatory

Plain FTP sends your password in clear text. In production, always use FTPS.

Server → Configure → FTP and FTP over TLS:

Use TLS: enabled
Allow plain FTP: disabled (in production)
Generate self-signed certificate (for testing) or import a Let’s Encrypt cert (.pem)

For Let’s Encrypt: see our Let’s Encrypt post — get a cert, import to FileZilla.

Connection test (client side)

FileZilla Client (or WinSCP):

Host: vds-ip or ftp.yoursite.com
Username: companymail
Password: yours
Port: 21 (FTP) or 990 (FTPS)
Encryption: Require explicit FTP over TLS (for FTPS)

Connect → user folder appears → upload/download to test.

Change password / delete user

Admin UI → Users → select → Edit / Remove.

Logs

Server → Configure → Logging:

Enable logfile ✓
File: C:\FileZillaServer\Logs\fzserver.log
Rotate daily

Connections, transfers, and errors are all logged. Critical for security audits.

Performance tip

For many concurrent transfers:

Server → Configure → Performance → Number of threads: 8-16

Disk I/O can bottleneck — NVMe SSD VDS is mandatory. KavesNET VDS plans all use NVMe.

Common errors

Can’t connect: Firewall (Windows + KavesNET) → are 21 and the passive range open?
“425 Can’t open data connection”: Passive mode not configured → Configure → set passive IP and port range
“Permission denied”: Mount point permissions wrong → ensure user folder has write rights
Slow upload: Antivirus may be scanning FTP traffic → add exception

Linux alternative: vsftpd / ProFTPD

On a Linux VDS, use vsftpd or ProFTPD instead of Windows FTP — CLI but lighter. SFTP (SSH FileZilla) is built into SSH; no extra install needed. See our SSH post.