SFTP is the secure successor to plain FTP: all files and login credentials are sent encrypted via SSH. In Plesk, you set this up in three steps: checking SSH access, creating an SFTP user, and then connecting with a client such as FileZilla or WinSCP. Below you’ll read exactly how this works and what to watch out for.
What is SFTP and why use it
SFTP (SSH File Transfer Protocol) sends files and login credentials encrypted over a single secure connection, unlike plain FTP, which sends everything unencrypted. Because SFTP uses SSH, traffic runs by default over port 22 and is protected against eavesdropping while in transit. For managing websites, uploading files, or making backups, SFTP is therefore the recommended method, especially if you work with sensitive customer data or login credentials for your web hosting.
Checking SSH access in Plesk
Before you can use SFTP, SSH must be available on your server. Log in to your Plesk control panel and check this as follows:
Log in to Plesk
Go to your Plesk control panel and log in with your account credentials.
Open Tools & Settings
Go to Tools & Settings and look for the section with server services or SSH settings.
Check SSH status
Verify whether SSH is active for your account or subscription. On managed servers, this is usually already configured correctly.
Note the port
By default, SSH/SFTP runs on port 22, unless your hosting provider has changed this for security reasons.
Not sure whether SSH is available for your subscription? Check the knowledge base or contact the support department.
Creating an SFTP user
Once SSH is available, create a user who is allowed to log in via SFTP. In Plesk, go to the Websites & Domains or Users section (depending on your Plesk version) and choose to add an FTP or SSH user.
- Username: choose something recognizable, such as the project name.
- Password: use a long, unique password or let Plesk generate one.
- Home directory: limit access to the folder that’s needed, for example the webroot of the domain.
- Access rights: make sure ‘SSH access’ or ‘shell access’ is enabled, otherwise SFTP won’t work.
Connecting with an SFTP client
With the created user, you can now connect via an SFTP client such as FileZilla, WinSCP, or Cyberduck. Enter the following details:
- Host: your domain name or the server’s IP address
- Protocol: SFTP β SSH File Transfer Protocol (not plain FTP)
- Port: default 22
- Username and password: the details of the user you just created
Click connect; with the correct configuration, you’ll immediately see the server’s folder structure and can upload, download, or edit files. For extra security, you can use an SSH key pair instead of a password: generate this in your client, upload the public key to the server, and enable passwordless login for the user.
Besides web hosting, do you also use business email hosting or manage multiple domain names under the same account? Then it’s smart to set up separate access for each service, so you maintain an overview of who has access to what.
Frequently Asked Questions
What is the difference between FTP and SFTP?
FTP sends data unencrypted, meaning passwords and files can be intercepted in transit. SFTP encrypts all traffic via SSH and is therefore the safer choice.
Which port does SFTP use?
By default, SFTP uses port 22, the same port as SSH. Some servers change this port to limit automated attacks.
Which SFTP client should I use?
FileZilla is free and user-friendly for Windows, macOS, and Linux alike. WinSCP is a good alternative for Windows users.
Can I use SFTP without Plesk?
Yes, SFTP works on any server where SSH is active. Plesk simply makes creating and managing users easier via a graphical interface.
Why can’t I log in via SFTP?
Check whether SSH access is enabled for the user, whether the correct port is being used, and whether the password was entered correctly without extra spaces.
Conclusion
Setting up SFTP in Plesk comes down to three steps: checking SSH access, creating a user with the right permissions, and connecting via a reliable client. This way you work with encrypted file transfer instead of vulnerable plain FTP.