Configuring an FTPS server

The server form is organized into sections to help you configure your connection step by step.

Server Details

Enter the server's hostname and the port your FTP server is listening on (if you haven't changed this you can leave this field blank and DeployHQ will use the default port 21).

Authentication

Enter your username and password.

Deployment Path

Enter the directory on the server where your files should be placed.

Advanced Options

Enable the option if the connection is Implicit. Next enable the option if necessary to Ignore TLS/SSL certificate errors (you will need to do this if you are connecting using a self signed certificate).

TLS version. We recommend selecting Auto-negotiate, which lets DeployHQ and your server agree on the highest TLS version both support. The Default option connects using TLS 1.0 only, for backwards compatibility with older servers — many modern hosts (including Azure App Service) refuse TLS 1.0, so if your connection fails during the TLS handshake, switch this to Auto-negotiate. You can also pin a specific version (TLS 1.0, 1.1, 1.2 or 1.3) if your server requires one.

Enable passive mode (PASV) if your server supports it, then if your FTP server doesn't report hidden files such as .gitignore by default, you can enable the option to Force the server to report hidden files.

Deploying to Azure App Service? See Configuring an Azure App Service server over FTPS for the TLS version, username format and publishing credentials that setup needs.

Parallel uploading (Beta) uploads files using multiple simultaneous connections for faster deployments. If your server does not support multiple connections, DeployHQ will automatically fall back to standard uploads. This feature requires beta features to be enabled on your account.