FortiGate Next Generation Firewall utilizes purpose-built security processors and threat intelligence security services from FortiGuard labs to deliver top-rated protection and high performance, including encrypted traffic.
Article Id 211965



This article describes common causes of errors where the SSL VPN stops negotiating at specific percentages and offers solutions.








The cause may vary depending on the percentage the negotiation stops at:


  1. 10%.
  • The error may be 'Unable to establish the VPN connection. The VPN server may be unreachable'.
  • The issue is usually due to a network connection.
  • Check whether the PC is able to access the internet and reach the VPN server on the necessary port.
  • Check whether the correct remote Gateway and port are configured in FortiClient settings.
  • Confirm whether the server certificate has been selected in FortiGate SSL VPN settings.
  • Check firewall policy to make sure there is at least one policy with Incoming Interface as SSL VPN tunnel interface (ssl.root).


  1. 31%.


  1. 40%.
  • This may occur when FortiClient generates a new pop-up window verifying whether the user wishes to proceed with a non-trusted TLS/SSL certificate.
  • It may mean a TLS version mismatch, which will also show as error -5029. If this message appears, there is a mismatch in the TLS version. Check if the TLS version that’s in use by the FortiGate is enabled on the client. Technical Note: How to limit the SSL and TLS versions of connections initiated by Forticlient explains how to check the TLS version.
  • An application or the FortiGate may cause this error. Check the local machine and network setup.


  1. 48%.


  1. 80%.
  • It may feature an error such as 'Unable to log on to the server. Your username or password may not be configured properly for this connection'.
  • Negotiation stops at this stage due to issues with user privileges.
  • If negotiation stops at this stage, check whether the username and password were entered correctly.
  • Check the user and user group. This issue often occurs if the user is not in the correct user group with VPN access.
  • The -14 error of around 80% could be because of a user/group mismatch between the SSL VPN authentication rules and the Firewall policy for SSL VPN.
  • It is possible to have user and group configured but it must be exactly the same in SSL VPN authentication rules and Firewall policy.
  • If a user has a configured user group in the SSL VPN settings, always configure the user group in the firewall policy.
  • Verify the user is also matching the correct portal.
  • This issue may occur if a corresponding policy for the users has not been configured.
  • Additionally, check whether the correct Realm is being used and if any are configured.
  • If a user tries to log in from the local/guest user make sure the 'Restrict to Specific OS Versions' is disabled.
  • Look for host check/ MAC address check/ AV check is enabled.


  1. 98%.
  • Issues at this stage usually occur due to a corrupted installation of FortiClient or due to OS problems.
  • Reinstall the FortiClient software on the system.
  • Check for compatibility issues between FortiGate and FortiClient and EMS.
  • This may also occur when attempting to negotiate SSL VPN with the free version of FortiClient.