Support Forum
The Forums are a place to find answers on a range of Fortinet products from peers and product experts.
rgros
New Contributor

forticlient 7.4.3.1736 on linux hangs on connecting

I have installed the latest forticlient package on my debian machine and configured it to connect to our vpn.

After providing my (correct) password, the status is changed to 'Connecting', a 'disconnect' button appears, but nothing happens. The status remains connecting for hours. In the terminal, this appears:

 

```

14:23:28.412 › IPC_RENDERER_REQUEST.LOADED
14:23:28.413 › WindowManager handleWindowLoaded
14:23:28.914 › WindowManager handlePossibleProtocolLauncherArgs argv=["/opt/forticlient/gui/FortiClient"]
14:23:28.914 › WindowManager handleCreateMainWindow
14:23:29.502 › Receive websocket type=FCT_UPDATE_TASK_DONE
14:23:32.949 › Receive websocket type=FCT_UPDATE_TASK_DONE
Error occurred in handler for 'keytar.deletePassword': [Error: Unknown or unsupported transport “disabled” for address “disabled:”]
```

 

Although I can find other posts about this, I could not find a solution. Any ideas?

Thanks in advance, Ruud

3 REPLIES 3
Jean-Philippe_P
Moderator
Moderator

Hello rgros, 

 

Thank you for using the Community Forum. I will seek to get you an answer or help. We will reply to this thread with an update as soon as possible. 

 

Thanks, 

Regards,

Jean-Philippe - Fortinet Community Team
AEK
SuperUser
SuperUser

Do you mean SSL VPN or IPsec?

 

First think you should do is to check if your connection attempt is reaching the remote FortiGate.

Run the following on the remote FGT:

diag sniffer packet any "host x.x.x.x" 4

Where x.x.x.x is the client public IP address.

 

If you receive the traffic on FGT on the right port (IPsec or SSL VPN), then you can try debug the VPN connection.

 

If it is IPsec, run this:

diagnose vpn ike log filter rem-addr4 x.x.x.x
diagnose debug application ike -1
diagnose debug application fnbamd -1
diagnose debug console timestamp enable
diagnose debug enable

 

If it is SSL VPN, run this:

diagnose vpn ssl debug-filter src-addr4 x.x.x.x
diagnose debug application sslvpn -1
diagnose debug application fnbamd -1
diagnose debug console timestamp enable
diagnose debug enable

 

Hope it helps.

AEK
AEK
rgros
New Contributor

thanks for your help. I use SSL VPN. I have no access myself to fortigate, but checking fortigate is a good starting point. I have made a request to the check the connection first. I know by experience this takes some time, but I let you know when I know more!

 

Announcements
Check out our Community Chatter Blog! Click here to get involved
Labels
Top Kudoed Authors