Setting up FTPS access

For bigger file operations, FTPS is the standard route into your webhosting. Every Plesk plan comes with a main FTP account, plus sub-accounts for staff / web designers. Here’s how to connect with FileZilla, Cyberduck and friends.

Important: FTPS, not FTP

We accept no unencrypted FTP. When logging in, you must select explicit FTP over TLS (FTPES) — otherwise you’ll get login errors.

That’s the standard today; every reasonable FTP client supports it.

Server details

From your Plesk order mail or under Websites & Domains → FTP Access:

• Host: typically web1.xaweho.de or your domain deinedomain.de
• Port: 21 (default)
• Encryption: explicit FTP over TLS (FTPES)
• Username: typically <deinedomain.de>_ftp or one you chose
• Password: from the Plesk mail (changeable in Plesk)
• Directory: chrooted to your Plesk home, you land in /

Setup with FileZilla

FileZilla.org — free for Mac, Windows, Linux.

1. File → Site Manager → New Site
2. Enter:
   • Protocol: FTP — File Transfer Protocol
   • Host: web1.xaweho.de (or your domain)
   • Port: 21
   • Encryption: Require explicit FTP over TLS
   • Logon type: Normal
   • User: your FTP username
   • Password: your FTP password
3. Connect

On the first connection, FileZilla asks about the server certificate → accept (we use Let’s Encrypt).

You land in the root directory of your Plesk home. httpdocs/ is your document root.

Setup with Cyberduck

Cyberduck.io — free for Mac, Windows.

1. Open Connection
2. Protocol: FTP-SSL (Explicit AUTH TLS)
3. Server, port 21, username, password
4. Connect

Cyberduck shows a file browser similar to Finder/Explorer.

Setup with Transmit (Mac)

panic.com/transmit — commercial, ~€50, very popular with Mac pros.

Setup is analogous: protocol FTPS, hostname, port 21, login.

CLI with lftp

For scripts and server-to-server sync:

lftp -u username,password ftps://web1.xaweho.de

Commands: ls, cd, put, get, mirror -R (recursive sync).

Example script:

#!/bin/bash
lftp -u $USER,$PASS ftps://web1.xaweho.de << EOF
mirror -R /local/website /httpdocs/
quit
EOF

Changing the FTP password

In Plesk: Websites & Domains → FTP Access → Change → enter the new password.

Takes effect immediately — all running FTP clients have to log in again.

FTP sub-accounts (for staff / web designers)

If you don’t want to hand your main FTP password to an external web designer:

1. Websites & Domains → FTP Access → +
2. Choose a username (unique)
3. Set a password
4. Restrict the home directory (e.g. only /httpdocs/wp-content/themes/ for a theme designer)
5. Permissions: read, write, manage

The sub-account is active immediately. When the project ends: delete it from the list.

Advantage: your main credentials stay secret, sub-accounts have a limited scope.

Active vs. passive connections

FTP uses two connections: control (port 21) and data (a separate port).

• Active: the server initiates the data connection — doesn’t work behind NAT/firewalls
• Passive: the client initiates both — today’s standard

In FileZilla → Edit → Settings → FTP → choose Passive. Cyberduck defaults to passive.

Performance

FTPS speed depends on:

• your upload bandwidth
• server load on our end (low)
• the number of concurrent files (FTP is slow with many small ones — rsync via SFTP is faster; SSH, and with it SFTP, is included in every plan)

From our experience: 10-50 MB/s is typical with a good internet connection.

Pitfalls

Connection fails despite correct login

• TLS mode enabled?
• Is port 21 open in your firewall?
• Test with a different tool — sometimes FileZilla has cached-server-cert problems

Broken file permissions

FTP transfers files with default permissions. If you upload a PHP script and it isn’t executable:

• In the Plesk File Manager → Permissions
• Or in the FTP client: right-click → Change file permissions (FileZilla supports this)

Hidden files not visible

In FileZilla: enable Server → Force showing hidden files. Otherwise you won’t see .htaccess.

Active vs. passive problems

On mobile networks or restrictive company networks: passive mode. For server-to-server workflows, active is sometimes better.

SFTP instead of FTPS?

SFTP runs over SSH and is included in every plan — even Start.

• Server: web1.xaweho.de
• Port: 22
• Username: SSH username (a separate Plesk setting)
• Password: SSH password

SFTP advantages: one port (22), no TLS setup, often faster with many small files.

Frequently asked questions

How many FTP sub-accounts can I create? In every plan you can create additional sub-accounts alongside the main account — for typical setups with a web designer or staff, that’s more than enough.

Can I restrict a sub-account’s permission to just one folder? Yes. In Plesk → sub-account → set the home directory to e.g. /httpdocs/uploads/. The sub-account only sees that folder.

FTPS logs — can I see who uploaded what and when? Plesk has Statistics → Logs → ftp.access.log. Shows login attempts and operations.

Multiple FTP connections in parallel — possible? Yes, but the server limits you to 8 concurrent connections per account. More sub-accounts if needed.

Can I revoke sub-account passwords without changing my main password? Yes, simply delete the sub-account or change its password. The main access stays.

FTP over a mobile network — does that work? Some mobile providers block port 21. Workaround: SFTP over port 22 (included in every plan) or the File Manager in the browser.

Auto-deployment via GitHub Actions / GitLab CI? Yes, with a sub-account and the password stored as a secret. SFTP recommended, FTPS as a fallback.

What happens with FTP brute-force attacks on my account? Plesk has Fail2Ban-style protection. After 3 failed attempts, the IP is blocked for 15 minutes. For repeated attacks from the same region: open a ticket, we’ll add extra blocks.

What’s next

• File Manager in the browser
• Migrating your website to xaweho
• Creating backups and restoring