Configuring an SFTP server

Pick ‘SFTP’ as the server type and give it an easily recognizable name.

Enter your server’s hostname, and optionally the SFTP port if you wish to use a different port (the default ‘22’ is standard for the SFTP protocol).

Enter your username, and you’ll then be presented with two choices in terms of authentication: an SSH key or a simple password.

Configuring an SSH server for deployment

If you opt for the former option, we’ll generate a public key for you as well as a one-liner that you may run on your server to add this key to the “authorized_keys” file.

It’s not uncommon for a shared hosting provider to offer semi-restricted SSH access, for which you’ll need to add the SSH key through the web interface offered by your hosting provider. In this case, copy the public key using the “copy the public key” link and add it through said web interface. Often, you’ll also have to whitelist our IP address or explicitly link it to the key address you’re adding. You’ll find the appropriate IP address in the “Server configuration” modal (note that this IP address might be different across projects or users).

Enter the upload path to which your files should be uploaded. This is the absolute path on the remote server. On DirectAdmin-based systems, for example, this path will look something like /home/<username>/domains/<domain>/public_html.

To figure out whether the server connection data is correct, run the server connection test and we’ll try to connect to your server and check the provided path(s).

We’ve also written an article outlining how to easily deploy code to an SFTP server.