How to connect with SFTP or FTPS and upload a website

SFTP and FTPS encrypt file transfers, but they use different services. SFTP uses SSH transport; FTPS adds TLS to FTP. A working FTP account does not establish that SFTP access is available. Use the protocol, hostname, port, and account details supplied for your hosting service. Virtualmin transfer methods

Prepare your connection #

Install a maintained file transfer client and create a saved connection. Select the specified protocol rather than allowing the client to fall back to unencrypted FTP. Enter your hosting transfer hostname and username exactly as supplied. Do not use your WordPress password unless you were told the accounts share credentials.

The Control Center's Hosting login shows the hosting owner username and a saved password when available. Use them for file transfer only if the supplied connection instructions identify that account. The panel URL is not a substitute for the transfer hostname and port. See hosting password help if those credentials changed.

Transfer the files #

1. Connect using the supplied port and authentication method. If the host supports key authentication, follow its process for registering your public key; keep the private key private.
2. Verify the SFTP server key fingerprint or FTPS certificate against trusted hosting details. Ask support about an unexpected identity change before continuing.
3. Locate the selected site's document root. A restricted account may display / as its starting directory even though that is only its permitted area.
4. Back up existing content, then upload a small test file with no private information.
5. Check the test file through the intended domain. Upload the rest of the site and review the client's failed-transfer queue.
6. Remove the test file and disconnect when finished.

Verify the result #

Check the home page, an internal page, and an image. Confirm that your client transferred hidden files that the application needs. Keep local and remote paths in view to avoid uploading a website inside an unintended second folder.

Troubleshooting #

Connection refused or timeout: Check protocol, hostname, and port; do not change the server firewall yourself.

Authentication failed: Confirm that this user has access to the chosen protocol. Stop repeated retries if an account block appears.

Permission denied: Check the assigned directory and ownership with support. Do not make the website writable to everyone.

FTPS connects but cannot list files: Send support the sanitized connection log; data-channel or passive-port configuration may require a host-side fix.

Related: create limited transfer accounts.