Use a file-transfer client that supports the encrypted protocol available for your service. Before connecting, confirm the hostname, protocol, port and account to use. Selecting a port number alone does not turn one protocol into another.
Choose the correct protocol
- SFTP: file transfer over SSH, commonly on port 22, although the server may use another port. Your account must have the required access. An additional FTP account created in cPanel does not automatically provide SFTP access.
- FTPS: FTP protected by TLS. Explicit mode commonly uses port 21 for the initial connection. The client must require encryption and use the settings supplied for the service.
Use the hostname confirmed by Nuagerie, including for a matching FTPS service certificate. Do not assume that adding “ftp” to your domain produces the correct address. For a small number of files, the control panel's File Manager may also be suitable.
Configure the connection and upload files
- Create a connection in your file-transfer client and explicitly select SFTP or FTPS.
- Enter the service settings and the intended account's credentials. Use the full username where required.
- Verify the FTPS certificate or SSH host-key fingerprint for a new connection. If the identity does not match or changes unexpectedly, have it confirmed before continuing.
- Open the remote directory for the affected website. This can differ between domains. Keep a recoverable copy of files you will replace.
- Select the local files and use the action that uploads them to the server. Review overwrite prompts before accepting them.
- Check for failed transfers, then open the website and verify the changed pages.
Transferring files does not automatically back up an application's database.
If the connection fails
Record the error message, protocol, port and time of the problem. Send these details through your Client Area, without passwords or private keys. Do not work around a certificate error by switching to an unencrypted connection.
Prepare your website for publication
Copying files can be one part of a larger deployment: the database, configuration, scheduled jobs and DNS may also need coordinated changes. Our team can help distinguish hosting access from application work so your developer has a clear basis for the release.
When planning a publication or transfer, identify the website, affected files and any database in your Client Area request. Use our staging guide to organize the tests. If you need a website developed or taken over, discuss the project with Nuagerie.
