Description
This article describes the required configuration to allow SSL VPN clients to communicate with another SSL VPN client.
Scope
FortiGate.
Solution
This article assumes that the SSL VPN is already configured and functional. To allow client-to-client SSL VPN traffic, create a new policy as shown below.
If split tunnel is enabled in the SSL VPN, add the SSL-VPN client subnet to the routing address list in the respective SSL VPN portal.
After making the changes, test the SSL VPN client-to-client communication. Ensure the client windows firewall allows this communication or disable or add exemption in windows firewall if not the communication between clients will not work
If the issue is not resolved , open a support ticket using the Fortinet Support Portal and include the following details:
ipconfig /all
route print
tracert <remote sslvpn client>
diagnose debug reset
diagnose debug flow filter addr x.x.x.x <----- Replace x.x.x.x with the source SSL VPN client IP.
diagnose debug flow filter proto 1
diagnose debug flow trace start 10000
diagnose debug enable
diagnose debug reset
diagnose debug disable
Note:
In FortiOS v7.6.3 and above, SSL VPN tunnel mode is not supported for any FortiGate model. In these firmware versions, SSL VPN web mode is renamed to 'Agentless VPN'. If SSL VPN is in use for remote access, it is strongly recommended to migrate to IPsec VPN before upgrading to a firmware version that removes support for SSL VPN tunnel mode.
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2026 Fortinet, Inc. All Rights Reserved.