FTP is the quickest way to transfer many files to and from your hosting. Your main DirectAdmin user can always use FTP, and FTP Management lets you add extra accounts for developers or clients that only see one folder.
Before you start
- An FTP client such as FileZilla or WinSCP.
- Your server hostname or domain name.
Create an FTP account
- Log in to DirectAdmin and select the domain at the top.
- Go to Account Manager → FTP Management.
- Click Create FTP Account.
- Enter the FTP Username. The full login becomes
name@example.com. - Set a strong password.
- Choose the Directory:
- Domain – the whole
domains/example.comfolder. - FTP – the
public_ftpfolder. - User – the user's own home area.
- Custom – any folder you type, for example
/home/john/domains/example.com/public_html/uploads.
- Domain – the whole
- Click Create.
Connect with FileZilla
- Open File → Site Manager → New site.
- Protocol: FTP. Encryption: Require explicit FTP over TLS.
- Host: your domain or server hostname. Port: 21.
- Logon type: Normal. User:
name@example.com(or the main DirectAdmin user name). Password: the FTP password. - Click Connect and trust the certificate.
If SSH is enabled for your account, you can also use SFTP on port 22 with your main DirectAdmin user, which is even more secure.
Manage accounts
- Click Change Password or Modify to update an account.
- Tick an account and click Delete when it is no longer needed. Files remain on the server.
FTP, FTPS or SFTP?
| Protocol | Port | Encrypted | Login |
|---|---|---|---|
| FTP | 21 | No | Any FTP account |
| FTPS (explicit TLS) | 21 | Yes | Any FTP account |
| SFTP | 22 (or custom SSH port) | Yes | Main DirectAdmin user with SSH enabled |
For day-to-day uploads FTPS is the best balance: it works for every FTP account you create and encrypts both the password and the files. If your client asks for a certificate decision, the server certificate is normally issued for the server hostname, so connecting with that hostname avoids warnings.
Security tips
- Never use plain FTP without TLS on public networks.
- Give each person their own login and remove it after the project.
- Do not store FTP passwords in plain text in shared documents.
Troubleshooting
- 530 Login authentication failed: use the full login
name@example.com, not justname. Reset the password if unsure. - Connected but directory listing times out: passive ports are blocked by a firewall. Try another network, or ask support to check the passive port range.
- Too many failed logins / blocked: DirectAdmin's Brute Force Monitor may have blocked your IP. Support can unblock it; see Brute Force Monitor.
- Permission denied on upload: the folder may be owned by a different user after a migration.
