Click OK/SAVE to save changes.

Click the CONNECT button to launch the connection.

You will be prompted with a pop-up regarding NON-TRUSTED CERTIFICATE, select the option to TRUST THIS CERTIFICATE and click OK.

CoreFTP
-----------------
CoreFTP versions tested: LE v2.1

In Site Manager, set the following parameters:
- SiteName: (set to anything you wish to call the connection)
- host: ftp.yourdomain.com (replace yourdomain.com with your actual domain)
- Username: your FTP username
- Password: your FTP password
- port: 21
- PASV: enable
- Connection: AuthTLS
SSL Options:
- SSL Listings: enabled
- SSL transfer: enabled

Click CONNECT to launch the connection.  You will be prompted with the Certificate information, click the ALWAYS ACCEPT button.

Firefox's FireFTP
-----------------
FireFTP versions tested: 1.0.6, 1.0.7

Set the following parameters:
On the MAIN tab:
- Account Name: (set to anything you wish to call the connection)
- host: ftp.yourdomain.com (replace yourdomain.com with your actual domain)
- Login: your FTP username
- Password: your FTP password
On the CONNECTION tab:
- Security: AuthTLS(Best)
- Port: 21
- Initial Directories-LOCAL: (optional, you can set this to the location of your website files on your local PC)
- Initial Directories-REMOTE: /httpdocs (httpdocs is where you will would need to publish your website files.. optionally, you can place nothing in this field, and it will show you all folders available within your ftproot/hosting space, i.e., cgi-bin, private, statistics, etc).

click OK/SAVE to save the changes.  Click CONNECT to launch the connection.

With FireFTP, you may receive the following warning messages:
- The certificate is only valid for X.X.X.X (the server's IP)
- The certificate does not come from a trusted source

These warnings are ok and expected.  To bypass these warnings and make your connection:
- click the YOU CAN ADD AN EXCEPTION button
- click the ADD EXCEPTION button
- click the GET CERTIFICATE button
- check the box for PERMANENTLY STORE THIS EXCEPTION
- click the CONFIRM SECURITY EXCEPTION button 

Generic FTP client instructions:
-----------------
ftp server/host: ftp.yourdomain.com (replace yourdomain.com with your actual domain)
port: 21
active/passive mode: passive (PASV) or epassive (EPASV)
FTPS/security options: the option for enabling FTPS may be called any of the following:
- AuthTLS
- AuthSSL
- FTP over SSL Explicit
- SSL Explicit
- AuthSSL-Explicit
(where specified, do not chose the "Implicit" option, only the "Explicit" option)

When making your connection, if you receive warning about the certificate, select the option to allow use of the certificate despite the warning.

 Verifying your FTPS connection was successfully made in a secure manner:

 When testing an FTPS connection… you can confirm you used SSL by checking the FTP log in your FTP client for the AUTH command (either AUTH SSL or AUTH TLS)… Here’s an example of what FireFTP logs for an FTPS connection:

220 WEB16.3Essentials.com FTPserver ready...
       AUTH TLS
234 AUTH command ok; starting SSL connection.
       PBSZ 0
200 PBSZ=0
       USER 18915
331 Password required for 18915.
       PASS (password not shown)
230 User 18915 logged in.

Versus what it logs for a standard FTP connection:

220 WEB16.3Essentials.com FTPserver ready...
       USER 18915
331 Password required for 18915.
       PASS (password not shown)
230 User 18915 logged in.

Notice the AUTH TLS command was the FIRST thing that was sent by the FTP client software to the FTP server – and the SSL connection was then negotiated and set up BEFORE the user/pw was even sent.

*FTP over SSL is not available on the following servers: web14, web12, web10, web8, web6, web4, web2, web5, web7.  If you are hosted on one of these servers and wish to use FTPS for file transfer, please contact the support team who will provide you options on moving to a server which supports this.