Description This article describes a possible troubleshooting step to
allow websites blocked as a result of Cloudflare encrypted client hello
(ECH) protocol. Scope FortiGate with DPI. Solution If some websites are
not accessible because of Cloudflare...
Description This article describes some hints on the email validation
process when configuring email collection for guest access on SSIDs.
Scope FortiOS with Email Collection SSIDs. Solution Start by configuring
the email collection on the relevant S...
Description This article describes accessing specific Internet
destinations when remote FortiClient users connect to dialup IPSec with
split tunneling enabled. Scope FortiOS, FortiClient. Solution Split
tunneling allows splitting Internet traffic fro...
Description This article describes FortiGate models supporting a
specific transceiver. Scope FortiOS with transceiver(s). Solution In
some cases, the user is interested in knowing which FortiGate models
support a specific transceiver model. Such info...
Description This article describes why 'Unknown user' is seen in FortiOS
7.2.x when remote users connect to a dial-up VPN tunnel using
FortiClient. Scope FortiOS 7.2.x. Solution In FortiOS 7.2.x, when a
dial-up IPsec VPN tunnel is configured for remo...
Would you please confirm if the following is what you've on configured
on fortigate: configure system central-management set type fortiguard
end In addition you can check this troubleshooting article:
https://community.fortinet.com/t5/FortiGate/Troub...
Try to use ZTNA rather than sslvpn as this is more secure as per:
https://docs.fortinet.com/document/fortigate/7.0.0/new-features/194961/basic-ztna-configuration
Hope this help
If the vlans are configured and attached to port2 you need to create
firewall policies from the VPN interface to each vlan to be able to
access resources on those vlans. Remember to add those vlans on
accessible networks under VPN phase-1. If those v...
You can disable any security software running on the client side and
check again. In addition you can run: diagnose sniffer packet any 'port
xxx' 4 <- xxx is the non working printers port number Also, diagnose
debug reset diagnose debug flow filter p...