
FortiGate SSL VPN Tunnel vs Web Mode: diagnose debug application sslvpn
- 3 days ago
- 2 min read

Web mode bookmarks open. FortiClient tunnel stays at 98%. Users say 'VPN is down' but web mode works.
This is a live-ticket style lesson from Techclick Infosec. You will isolate the fault with CLI first, then prove the fix with one clean packet or log.
What you will be able to do
Name the first CLI command to run on FortiGate for this ticket
Separate the layer that is actually broken from the layer people blame
Apply one scoped fix instead of a global disable
Prove the ticket closed with a session, log, or counter
Quick answer
Web mode is reverse proxy. Tunnel mode is a full adapter. Debug sslvpn and check the tunnel IP pool, split-tunnel, and FortiClient version.
Why this ticket shows up
A healthy web mode only proves auth and HTTPS. Tunnel mode can fail on IP pool exhaustion, DTLS, or a host-check.
Symptoms operators actually see
Web mode OK, tunnel stuck
IP pool exhausted
DTLS blocked on the path
Host-check antivirus rule fails
CLI first — copy this block
Run these on the FortiGate device or console named in the ticket. Do not skip the first show command — it tells you which later command matters.
get vpn ssl monitor
diagnose firewall ippool list
diagnose debug application sslvpn -1
diagnose debug enable
diagnose vpn ssl list
get vpn ssl settingsHow to read that output
ssl monitor shows how many tunnel users versus web users. An empty tunnel pool with free web sessions is the giveaway.
Triage order
Compare web vs tunnel counts
Check the tunnel IP range for collisions
Read sslvpn debug during one failed connect
Disable host-check only as a test
Fix DTLS or fall back to TLS
Classic traps
What you see | Real cause | Fix |
Rebuild the whole SSL VPN | Pool is exhausted | Grow the pool |
Open UDP 443 everywhere | DTLS is optional | TLS may be enough |
Blame FortiClient | Portal is tunnel-only for that group | Check portal mapping |
Proof the ticket is closed
Tunnel user appears in ssl monitor with an IP
Internal ping works
Web mode still works
Say this in an interview
Web mode success is not tunnel success. I read the IP pool before I reinstall FortiClient.
Need the full vendor lab, mock interview, and production runbooks? Techclick trains Palo Alto, Zscaler, F5, FortiGate, Check Point, Cisco ISE, Azure and routing with live CLI — start at https://www.techclick.in/



Comments