Description |
This article describes how to resolve an issue where, when using FTPS through an explicit proxy on FortiProxy, users encounter an SSL handshake failure between FortiProxy and the server. |
Scope | FortiProxy running versions 7.2.8 and earlier |
Solution |
This problem happens because the Web Application Delivery (WAD) process returns a 2xx response to the client before the data connection with the FTPS server is totally established, leading to connection failure. Symptoms:
Cause: The WAD process on FortiProxy returns a 2xx response to the client too early, before the SSL handshake and data connection with the FTPS server are fully established. This results in an incomplete SSL handshake and a failed connection.
Definitive Solution: This issue has been resolved in the following versions:
FortiProxy 7.4.4 release notes. Workaround: A possible workaround is to create a specific proxy policy for the FTPS server's IP address and place it at the top of all other policies. However, do not include a deep inspection profile in this policy. Important Note:
Adding the FTPS server to the decryption exception list may require leaving the security policy more open to enable static setup of the data channel. This configuration allows FortiProxy to accept the connection with explicit encryption while stopping the decryption process. |