SFTP
Provide secure file-transfer access and inspect account transfer settings.
1Overview
SFTP uses SSH transport and the hosting account identity. It is distinct from FTP accounts and is the preferred encrypted transfer method for administrators and customers.
2Before you begin
Administrator actions can affect multiple customer accounts and server services.
3Step-by-step workflow
Open SFTP or the account tools, confirm the host, port, username, and allowed directory, then connect with the hosting password or configured SSH key. Use the account home or documented files path as the transfer root.
- Open SFTP and select the hosting account whose connection details you need.
- Choose Show connection to display the server, port, username, and allowed path.
- In the file-transfer client, select SFTP as the protocol rather than FTP.
- Use the displayed SSH port and the hosting account username.
- Authenticate with the approved hosting password or a supported SSH key.
- Confirm the starting directory before transferring any website files.
- Upload a harmless test file in an approved folder and confirm its ownership and permissions.
- Remove the test file and revoke access that is no longer needed.
4Practical example
Example: an SFTP login normally uses the hosting account identity. A separately created FTP account has its own login and password and connects through explicit FTP over TLS, normally on port 21.
5Verify the result
Validate the outcome from the affected account or an independent client connection, not only from the administrator screen.
- Upload and remove a harmless test file in an approved directory.
- Confirm the account cannot browse outside its intended home or files path.
6Common problems and what to check
Connection refused: check the displayed SSH port and any provider firewall.
Authentication fails: confirm the hosting username and credential instead of using the panel administrator login.
A directory is inaccessible: review its account ownership and allowed jail path; do not change entire hosting trees to writable permissions.
7Security, impact, and rollback
Do not send passwords in plain text. Use SSH keys where supported and remove access when a contractor or integration no longer needs it.