+- AdminsForum (https://adminsforum.com)
+-- Forum: Free & open-source control panels (https://adminsforum.com/Forum-free-open-source-control-panels)
+--- Forum: aaPanel (https://adminsforum.com/Forum-aapanel)
+---- Forum: aaPanel Guides & Tutorials (https://adminsforum.com/Forum-aapanel-guides-tutorials)
+----- Forum: aaPanel FTP, SFTP & File Transfer Guides (https://adminsforum.com/Forum-aapanel-ftp-sftp-file-transfer-guides)
+----- Thread: Guide Connect FileZilla to aaPanel with Secure FTPS (/Thread-guide-connect-filezilla-to-aapanel-with-secure-ftps)
Connect FileZilla to aaPanel with Secure FTPS - DEV - 10-13-2026
Quick answer
Use FileZilla Site Manager with protocol FTP, port 21 and “Require explicit FTP over TLS”. Enter the hostname covered by your server certificate and a separate restricted FTP account. SFTP is an SSH connection and uses different server credentials; it is not a Pure-FTPd account.
Before connecting
Complete the FTPS server setup first. Confirm the service is running, the certificate is valid and your FTP account points to the correct directory. Install FileZilla Client from its official website. You need the Client application, not FileZilla Server.
1. Create a saved site
Open File → Site Manager, or press Ctrl+S. Choose New Site and give it a recognizable label such as “AdminsForum lab — FTPS”. Select the General tab and enter your own server details. The following reference shows our lab settings, not a screenshot of a running FileZilla session.
- Host: mail.adminslab.com in our lab. Enter your certificate hostname without https:// or a folder path.
- Port: 21 for this explicit FTPS setup.
- Protocol: FTP — File Transfer Protocol.
- Encryption: Require explicit FTP over TLS. Avoid an option that falls back to unencrypted FTP.
- Logon type: Ask for password, so the saved site does not need to store it permanently.
- User: your separate restricted FTP username; af_ftp_lab in our test.
2. Check the certificate
The server identity must match the hostname you entered. If the certificate is expired, belongs to a different name or has an incomplete chain, stop and correct the server configuration. Do not routinely accept an unrelated certificate just to make the connection work.
Our backend test accepted the normal certificate chain and mail.adminslab.com hostname, negotiated TLS 1.3 and used encrypted data connections. That server test used a Python FTPS client; this article does not claim that FileZilla desktop screenshots or transfers were captured.
3. Understand the two file panes
The local pane displays files on your computer. The remote pane displays files the FTP account is allowed to access on the server. A restricted account's remote / means its assigned folder, not the Linux server's real root directory.
Our account is restricted to /www/wwwroot/adminslab.com/ftp-lab. Do not try to enter another website path as a workaround. If you need another folder, have the administrator assign the correct scope rather than using a root login.
4. Upload a harmless test file
Create a small text file on your computer named ftp-check.txt with a unique sentence. In the remote pane, confirm you are in the intended test folder. Drag the file from the local pane into that folder, or use the file's Upload action.
Check the transfer queue. The transfer should complete and appear in the successful list. Refresh the remote directory and confirm the filename and size. Do not test by overwriting a live index.php, wp-config.php or another production file.
5. Download and compare
Download the uploaded file into a different local folder. Open it and compare the sentence with the original, or compare its SHA-256 hash. A successful login alone does not prove that the data connection works; an upload and matching download provide a stronger check.
The lab's certificate-verifying FTPS test confirmed matching uploaded/downloaded contents and hash. It also refused access outside the assigned root.
6. Disconnect and keep credentials private
Disconnect when finished. Keep the test file only if it is useful for the lab; do not remove other server files. Never share an exported Site Manager configuration without checking whether it contains saved passwords or private server information.
Common connection problems
- Connection refused or timeout before login: check that Pure-FTPd is running, DNS points to the server and the configured control port is reachable.
- Login rejected: verify the username, password and enabled account. An FTP account is not automatically an SSH user.
- Login works but directory listing hangs: check Passive mode, the server's actual passive port range and both server/provider firewalls. Our lab range is 39000–40000; use your configured range.
- Plaintext connection rejected: expected with TLS 3. Select explicit FTPS and require encryption.
- Certificate name mismatch: use the certificate hostname, not an unrelated domain or raw IP.
- Permission denied on upload: confirm the assigned directory and filesystem ownership. Do not solve it by applying world-writable permissions across the server.
FTP, FTPS or SFTP?
FTP without TLS exposes login and file traffic. FTPS adds TLS to FTP and uses separate control/data connections. SFTP transfers files through SSH, normally over the server's SSH port. Select the protocol that matches the service you configured; changing a dropdown does not create that service or account.
Reference: FileZilla Site Manager documentation. © AdminsForum.