The Connections are managed by Add/Edit Job -> Tasks -> Add/Edit -> Task type selecting "FTP" and then selecting the FTP tab -> Add and finally clicking on the Manage connections button or from the main menu Manage -> Manage Connections. Connections are global, thus if you change a connection definition, this will affect all commands associated with this connection.
The Manage Connections window views a list of all configured connections - a Connection is a set of properties that can be used for FTP, FTPS, SFTP, SSH, and SMTP. Click on Add to add a new connection.
Main settings tab
Protocol type
VisualCron is able to connect using regular FTP and FTPS (with implicit and explicit encryption). Regular FTP offer no security and information is not encrypted. VisualCron supports both SSL 3.0 and TLS (SSL 3.1). SSL and TLS are protocols layered above connection protocols (such as TCP/IP) but beneath application protocols (such as FTP) that provide encrypted, authenticated communications between a client and a server.
Implicit versus explicit SSL connections (per RFC 2228)
Connecting securely and authenticating are two distinct methods of establishing a secure connection with a FTP server. In the first case, the Secure FTP server may first require a SSL connection to be established, before the initial welcome message is sent. This is called an implicit SSL connection. In the second case, the connection is established in clear text and a special FTP command must be sent to the Secure FTP server to change the connection into a secure connection. This is called an explicit SSL connection.
In most cases, FTP servers that support SSL authentication will accept a normal connection on port 21. Once the connection is established, it is necessary to authenticate before logging in, using the Authenticate method. When explicitly securing the connection, it is also possible to secure data connections using the overload of the Authenticate method which requires a DataChannelProtection ENUM as a parameter.
Servers that require an implicit SSL connection usually listen on port 990 rather than 21.
SFTP
SFTP (SSH File Transfer Protocol, often called Secure File Transfer Protocol) is a protocol that lets you transfer files securely over SSH connection. SFTP is not compatible with FTP (File Transfer Protocol), which has it's own security enhancements such as FTPS, FTP over SSL. SFTP is built on top of SSH connection. SSH supports various authentication schemes such as password-based and public key. Public key authentication requires a private key which can be linked to from the Security tab. The VisualCron implementation supports 3-5 of SFTP protocol (versions 1, 2 are outdated and not used anywhere). Default port for SFTP is 22.
Name
This is a descriptive name of the connection to distinguish from other connections.
Address
This is the host address to the server. It could be a DNS name or IP number.
Port
This is the remote connection port. Default port for regular FTP is 21. Default port for Implicit FTPS is 990.
Timeout
Sets the timeout for the operation.
Security tab
Authentication type
Authentication type can either by password or public key. For the FTP protocol only password authentication is available. When using SFTP together with public key authentication you have to specify a path to a private key file.
Anonymous
If your connection does not require a username and password this box should be checked.
Username
The username for the connection.
Password
The password for the connection.
Keys tab
The public key authentication requires you to have a public key on your SSH/SFTP server. To access that you need to specify a path to the private key that was generated by you at your server or through other client. At creation time you specify if you want to use a password along with the key, if not, leave the password blank.
Private key file
The local path to the private key file.
Password
If the private key file requires a password then enter it here, otherwise leave blank.
Certificates tab
A certificate is a digitally signed statement from one entity (person, company, etc.) that states that the public key of another entity has a particular value. Trusting the certificate's signature implies that you trust that the association in the certificate between the specified public key and the other entity are authentic.
Client certificates
Client certificates can be sent to the FTP server when connecting (implicit SSL) or when authenticating (explicit SSL). If the client certificate should be rejected by the server, an exception will be issued and the task can not continue.
To add a client certificate, you need to select one by clicking on the file icon button next to the Client certificate file text box or add a link to a certificate manually. Certificates can be of format *.cer, *.pem or *.pfx. When using *.pfx you can supply a password in the text box next to Certificate password.
Server certificates
The certificate that is received from the FTP server is verified against the VerificationFlags provided at connection or authentication. By default, if a certificate received from an FTP server contains anomalies, it will be rejected. If no anomalies are detected, it will be accepted. This behavior can be overridden by checking the Auto-accept server certificates checkbox. If not checked and a certificate anomaly is detected, a popup will be shown (if the client is logged in). The popup message will show why the server certificate was initially connected. You can choose to "Accept" or "Deny" the certificate. If accepted, it will be saved and you will not be asked again unless the server certificate has changed.
Proxy tab
Proxy servers allow a client to make indirect network connections. The client connects to the proxy, makes a request for a connection, file, etc. The proxy server then provides this resource by getting it from the requested address or by retrieving it from its cache. The advantages of using a proxy server can include filtering, connection sharing, increased speed and decreased bandwidth use. HTTP proxy servers are web servers that relay requests from a client to an external FTP server.
Proxy type
The FTP implementation in VisualCron currently only supports HTTP proxy. If you require other proxy types then contact support. The SFTP implementation supports SOCKS4 and SOCKS5 besides HTTP proxy.
Address
Host name or IP number of the proxy server.
Port
Port of the proxy server.
Username
A username to access the proxy server.
Password
A password to access the proxy server.
Extra settings tab
Data connection type
This value is indicating if the FTP client should initiate the data connection rather than the FTP server.
If set to PASV, the PASV command will be sent to the FTP server rather than the PORT command. This results in that the FTP server will listen on a data port (other than its default) and wait for a data connection to be established by the FTP client. The reply to the PASV command includes the host and port address the FTP server is listening on.
If set to PORT, the PORT command will be sent and the FTP client will listen for an incoming data connection.
The FTP server will establish the data connection upon receipt of a transfer command.
Note: If you are having problems with connecting or sending/receiving files to/from a server, try the PASV setting.
Log tab
The log tab provides features to debug/trace the connection.
Log outgoing messages to task output
All messages sent from VisualCron to the FTP server is logged and stored in the task output.
Log incoming messages to task output
All messages received from VisualCron to the FTP server is logged and stored in the task output.