Skip to main content
SivanathanK
New Member
April 8, 2026
Question

Unable to connect the VPN after upgraded the Forticlient VPN from 7.4.3 to 7.4.5 managed by EMS

  • April 8, 2026
  • 2 replies
  • 321 views

Dear Team,

One of our customer upgraded the FortiClient version from 7.4.3 to 7.4.5 which is managed by EMS.

After that most of the users facing to connect the VPN.

By default, the FortiClient installer contains 9 VPN URLs or Gateway defined in EMS.

When the user tried to connect any of the VPN gateway by clicking 'connect' button it does not react anything.

For some users, the issue resolved by reinstalling the FortiClient, Re-register the zero trust telemetry with invitation code, restarting the laptop and connecting to different Wifi or network.

For few users, did not helped any of the above workaround.

From the user machine we collected the FortiClient log and found below logs.

Could any one help with below logs to sort out the issue.


sslvpndaemon_1.log
[2026-04-07 08:36:49.9130356 UTC+02:00] [10616:6788] [sslvpndaemon 285 debug] TunnelInitiator::StartConnection() called.
[2026-04-07 08:36:49.9134374 UTC+02:00] [10616:6788] [sslvpndaemon 287 debug] TunnelInitiator::StartConnection() tunnel: <VPN Gateway Name>, session id: 1
[2026-04-07 08:36:49.9232315 UTC+02:00] [10616:6788] [sslvpndaemon 105 warning] fortivpn::SessionImpersonation::session_id_to_string() To be implemented.
[2026-04-07 08:36:49.9253913 UTC+02:00] [10616:6788] [sslvpndaemon 161 debug] fortivpn::SessionImpersonation::push impersonated 1 ()
[2026-04-07 08:36:49.9306548 UTC+02:00] [10616:6788] [sslvpndaemon 458 error] TunnelInitiator::StartConnection() could not get sorted server
[2026-04-07 08:36:52.0065593 UTC+02:00] [10616:1948] [sslvpndaemon 657 warning] CListener::_ReceiveMessage() got exit event.
[2026-04-07 08:36:52.0065596 UTC+02:00] [10616:2068] [sslvpndaemon 657 warning] CListener::_ReceiveMessage() got exit event.
[2026-04-07 08:36:52.0065573 UTC+02:00] [10616:20044] [sslvpndaemon 657 warning] CListener::_ReceiveMessage() got exit event.
[2026-04-07 08:36:52.0065591 UTC+02:00] [10616:18196] [sslvpndaemon 657 warning] CListener::_ReceiveMessage() got exit event.
[2026-04-07 08:36:52.0066043 UTC+02:00] [10616:14508] [sslvpndaemon 523 debug] FortiSslvpnD: PipeServerProc exits
[2026-04-07 08:36:52.0066722 UTC+02:00] [10616:24684] [sslvpndaemon 657 warning] CListener::_ReceiveMessage() got exit event.
[2026-04-07 08:36:52.7388065 UTC+02:00] [10616:13360] [sslvpndaemon 359 info] VpnConn shared memory uninitialized
[2026-04-07 08:36:52.7388165 UTC+02:00] [10616:13360] [sslvpndaemon 1418 info] trace stopped

FortiVPN_1.log
[2026-04-07 08:36:49.8868709 UTC+02:00] [13444:13628] [FortiVPN 79 info] fortivpn::ISSLVPNCommand_Impl::ConnectVPN() "Fortitray" is attempting to connect "<VPN URL>" in session 1
[2026-04-07 08:36:49.8868780 UTC+02:00] [13444:13628] [FortiVPN 81 info] fortivpn::ISSLVPNCommand_Impl::ConnectVPN() Attempting to connect to address "<VPN URL>:443"
[2026-04-07 08:36:49.8991046 UTC+02:00] [13444:13628] [FortiVPN 92 info] fortivpn::ISSLVPNCommand_Impl::ConnectVPN() system tray reports that "<VPN Gateway Name>" is connecting in session 1
[2026-04-07 08:36:49.9380204 UTC+02:00] [13444:13628] [FortiVPN 2086 error] fortivpn::StateMachine::HandleTunnelConnectFailed session 1's (Domain\User) vpn connection failed (reason: "Failed Internal Error")
[2026-04-07 08:36:49.9381022 UTC+02:00] [13444:13628] [FortiVPN 2164 warning] !! fortivpn::StateMachine::HandleTunnelConnectFailed tunnel connect failed with "Failed Internal Error".
[2026-04-07 08:36:49.9381054 UTC+02:00] [13444:13628] [FortiVPN 2166 warning] !! fortivpn::StateMachine::HandleTunnelConnectFailed restarting SSLVPN Daemon.
[2026-04-07 08:36:50.3230842 UTC+02:00] [13444:15488] [FortiVPN 390 warning] fortivpn::IFortiVPN_Impl::UpateSslVPNState() connection name is empty.
[2026-04-07 08:36:51.3361015 UTC+02:00] [13444:15488] [FortiVPN 390 warning] fortivpn::IFortiVPN_Impl::UpateSslVPNState() connection name is empty.
[2026-04-07 08:36:52.3349305 UTC+02:00] [13444:15488] [FortiVPN 390 warning] fortivpn::IFortiVPN_Impl::UpateSslVPNState() connection name is empty.
[2026-04-07 08:36:53.3457957 UTC+02:00] [13444:15488] [FortiVPN 390 warning] fortivpn::IFortiVPN_Impl::UpateSslVPNState() connection name is empty.
[2026-04-07 08:36:54.3601494 UTC+02:00] [13444:15488] [FortiVPN 390 warning] fortivpn::IFortiVPN_Impl::UpateSslVPNState() connection name is empty.
[2026-04-07 08:36:55.3684835 UTC+02:00] [13444:15488] [FortiVPN 390 warning] fortivpn::IFortiVPN_Impl::UpateSslVPNState() connection name is empty.
[2026-04-07 08:36:56.3709249 UTC+02:00] [13444:15488] [FortiVPN 390 warning] fortivpn::IFortiVPN_Impl::UpateSslVPNState() connection name is empty.
[2026-04-07 08:36:56.8768179 UTC+02:00] [13444:13628] [FortiVPN 2396 info] fortivpn::StateMachine::HandleTunnelDisconnected "Germany (National)" is disconnected.
[2026-04-07 08:36:56.9986040 UTC+02:00] [13444:13628] [FortiVPN 275 error] Failed to send pipe msg to gui. nRet=-5
[2026-04-07 08:36:56.9987335 UTC+02:00] [13444:13628] [FortiVPN 2437 info] fortivpn::StateMachine::HandleTunnelDisconnected disconnection reason: 20, ("Failed Internal Error")
[2026-04-07 08:36:56.9987426 UTC+02:00] [13444:13628] [FortiVPN 2462 error] !!! fortivpn::StateMachine::HandleTunnelDisconnected session 1's tunnel "<VPN Gateway Name>" disconnected unexpectedly!
[2026-04-07 08:36:57.0003216 UTC+02:00] [13444:13628] [FortiVPN 2466 info] fortivpn::StateMachine::HandleTunnelDisconnected this was not an internal connection cancellation
[2026-04-07 08:36:57.0003305 UTC+02:00] [13444:13628] [FortiVPN 2476 info] fortivpn::StateMachine::HandleTunnelDisconnected Notifying gui this was a connection error

 

Thanks!

 

2 replies

AEK
SuperUser
SuperUser
April 9, 2026

Hello

Which FortiClient version are you using?

Sometimes a FortiOS update may drop some old weak ciphers.

If you update your FortiClient to a newer version it may work.

AEK
SivanathanK
New Member
April 10, 2026

Hi,

We are using Forticlient 7.4.5 version.
If this is related to weak ciphers, Some time it worked once restarted or connect with different Wifi.