Skip to main content
maddyshah
Visitor III
June 13, 2025
Question

Unable to Establish VPN Connection and stuck at 10

  • June 13, 2025
  • 3 replies
  • 835 views
 

Iam getting this error, its working on other pcs but not on mine, i even disabled wirewall and windows defender but that also didnt help, i tried connecting to other internet connections, even mobile data, still getting the same issue, the creds are completely working .. working on other pcsScreenshot 2025-06-13 140344.png

3 replies

AEK
SuperUser
SuperUser
June 13, 2025

Hi Syed

10% could mean you are not even reaching the remote VPN IP:port.

https://community.fortinet.com/t5/FortiGate/Troubleshooting-Tip-Possible-reasons-for-FortiClient-SSL-VPN/ta-p/211965

You can try from web browser with https://IP:port to confirm if it is reachable or not.

AEK
maddyshah
maddyshahAuthor
Visitor III
June 15, 2025

Yes when i do https://110.38.225.213:4321 it redirect me to login page, telnet is also successful, I have other pcs connected to same network, connect to the VPN easily,I cant

AEK
SuperUser
SuperUser
June 15, 2025

Did the tech tip share above help?

Check all possible causes listed in "1" (10%).

AEK
jiahoong112
Staff
Staff
June 16, 2025

is your device able to ping the remote gateway or if the remote gateway used is an fqdn, are you able to resolve the dns of it? Check whether the configured sslvpn port on your FortiClient is correct or not.

 

Run these debugs on your Fortigate and reproduce the issue:

> If you do not see any relevant sslvpn debugs on the Fortigate, there is a high chance that the packets from your device are not even reaching Fortigate in the first place.

diag debug console timestamp enable
diag vpn ssl debug-filter src-addr4 x.x.x.x ==> x.x.x.x should be the public ip of the client that is connecting: whatismyip.com
diag debug application sslvpn -1
diag debug application fnbamd -1
diagnose debug enable

 

-> Reproduce issue

 

Disable debug:

# diag deb dis

diag deb reset