FTP/SSL Self-Signed Certificate

[kiddailey]

Not sure if this is user error or a bug, but I'm having an issue FTP over SSL with a self-signed certificate.

I recently switch an existing FTP connection to require SSL with a self-signed certificates. Works great in other FTP clients.

When my scheduled task runs in Syncovery, it tries to connect but aborts and complains about the self-signed certificate. It instructs me in the message field to run the task manually and accept the certificate stating specifically: "ERROR: SSL Server unknown - run manually to verify server"

When I try to run it manually though, it gives me an expected "Can't find authority" error but doesn't allow me to accept the certificate. Instead it just fails and retries stating: "Cannot access ftp://... (The Local Security Authority cannot be contacted at 00E30E0D)" and a second dialog sometimes pops up saying the same thing, but with an additional "EPrepException at 010FB8F6/"

If I click the "Browse" button next to the "Internet" button in the task profile connection settings, I get the same errors.

I'm hoping I'm just missing something. Any insight or assistance that can be provided to help me determine if it's user error or not would be greatly appreciated.

[superflexible]

This is an incompatibility of the FTP library 1 and your Windows version.

Please choose library 2 or 3. The option is on the FTP dialog.

[kiddailey]

Thank you! Worked like a charm.