dl-breadcrumbs__homedl-breadcrumb-item__separatorConfiguration and programmingdl-breadcrumb-item__separatorConfiguration in Automation Builderdl-breadcrumb-item__separator...dl-breadcrumb-item__separatorProtocols and special serversdl-breadcrumb-item__separatorSecure protocolsdl-breadcrumb-item__separatorConfiguring secure protocolsdl-breadcrumb-item__separatorSecure FTP
dl-pagination__prev-inactivedl-pagination__prev-activedl-pagination__next-inactivedl-pagination__next-active
Secure FTPdl-permalink__symbolPermalink

  1. Import a certificate to the PLC for FTP or create a self-signed certificate.

    Ensure the PLC clock is set to the current time and date when using certificates on the PLC. Otherwise the certificate cannot be used to secure a protocol (see also ⮫ “AC500 battery” and ⮫ “(S)NTP client configuration”).

  2. Add an FTP server to either ETH1 or ETH2

  3. Set the parameter “Security Mode” to either “BOTH” or “FTPS only”.

    You can use any FTP client that supports FTPS explicit mode (FTPES).

In case you are using a self-signed certificate, the FTP client will show some warnings or notice that it does not know the certificate and wants you to check it.

⮫ Further information