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

FortiClient VPN on MacOS Monterey - error code: -121

I upgraded to test the beta version of Monterey. 

FortiClient6.0.9.162

 

The VPN connection terminates unexpectedly! (Error Code: -121)

 

 

20210721 10:59:08.513 [sslvpn:INFO] unknown:0 dns suffix: 20210721 10:59:08.513 [sslvpn:INFO] unknown:0 epctrl ping server: 20210721 10:59:08.514 [sslvpn:INFO] unknown:0 xml parsing split tunnel info 20210721 10:59:08.514 [sslvpn:INFO] unknown:0 xml parse split tunnel info success. Buffer length: 94 bytes 20210721 10:59:08.514 [sslvpn:INFO] unknown:0 blocked all ipv6 traffic 20210721 10:59:08.515 [sslvpn:INFO] unknown:0 begin io loop 20210721 10:59:08.515 [sslvpn:INFO] unknown:0 launch ssl read thread 20210721 10:59:08.515 [sslvpn:INFO] unknown:0 launch tty read thread 20210721 10:59:08.515 [sslvpn:INFO] unknown:0 ssl read thread started 20210721 10:59:08.516 [sslvpn:INFO] unknown:0 main thread waiting for threads termination 20210721 10:59:08.516 [sslvpn:INFO] unknown:0 tty read thread started 20210721 10:59:08.516 [sslvpn:INFO] unknown:0 ssl write thread started 20210721 10:59:08.516 [sslvpn:INFO] unknown:0 tty write thread started 20210721 10:59:08.536 [sslvpn:INFO] unknown:0 pppd may die...trying to fix it 20210721 10:59:08.536 [sslvpn:INFO] unknown:0 pppd may die...trying to fix it 20210721 10:59:40.617 [sslvpn:EROR] unknown:0 ppp interface is not up, so terminate sslvpn 20210721 10:59:40.618 [sslvpn:INFO] unknown:0 reveive SIGUSR1 signal 20210721 10:59:40.617 [sslvpn:INFO] unknown:0 reveive SIGUSR1 signal 20210721 10:59:40.618 [sslvpn:INFO] unknown:0 reveive SIGUSR1 signal 20210721 10:59:40.618 [sslvpn:INFO] unknown:0 reveive SIGUSR1 signal 20210721 10:59:40.623 [sslvpn:INFO] unknown:0 io loop finished 20210721 10:59:40.623 [sslvpn:INFO] unknown:0 io finished, kill pppd 20210721 10:59:40.624 [sslvpn:INFO] unknown:0 kill_child:1144 20210721 10:59:40.624 [sslvpn:INFO] unknown:0 tunnel shutdown 0 20210721 10:59:40.624 [sslvpn:INFO] unknown:0 sslvpn starts to clean up 20210721 10:59:40.626 [sslvpn:INFO] unknown:0 sslvpnd terminated

2 Solutions
AlmightyBob

been trying on builds since beta 2 including yesterday's (27 July) release w/ no success. unfortunately we have to run vmware and go through a windows or ubuntu vm to get into the office.

 

the logs just show an extensive amount of this (below, over and over) followed by some IPv6 failed attempts just before it fails to connect.

 

Running on an intel 2019 macbook pro.

 

<?xml version='1.0' encoding='utf-8'?><sslvpn-tunnel ver='2' dtls='1' patch='1'><dtls-config heartbeat-interval='10' heartbeat-fail-count='10' heartbeat-idle-timeout='10' client-hello-timeout='10' /><tunnel-method value='ppp' /><tunnel-method value='tun' /><fos platform='FG100D' major='6' minor='02' patch='2' build='1010' branch='1010' /><auth-ses check-src-ip='1' tun-connect-without-reauth='0' tun-user-ses-timeout='30' /><client-config save-password='off' keep-alive='off' auto-connect='on' /><ipv4><dns domain='...' /><dns ip='...' /><dns ip='...' /><assigned-addr ipv4='...' /></ipv4><idle-timeout val='0' /><auth-timeout val='28800' /></sslvpn-tunnel>
----
20210714 12:37:01.778 [sslvpn:INFO] unknown:0 dns suffix: ...
20210714 12:37:01.778 [sslvpn:INFO] unknown:0 epctrl ping server:
20210714 12:37:01.778 [sslvpn:INFO] unknown:0 begin io loop
20210714 12:37:01.778 [sslvpn:INFO] unknown:0 launch ssl read thread
20210714 12:37:01.779 [sslvpn:INFO] unknown:0 launch tty read thread
20210714 12:37:01.779 [sslvpn:INFO] unknown:0 ssl read thread started
20210714 12:37:01.779 [sslvpn:INFO] unknown:0 main thread waiting for threads termination
20210714 12:37:01.779 [sslvpn:INFO] unknown:0 ssl write thread started
20210714 12:37:01.779 [sslvpn:INFO] unknown:0 tty read thread started
20210714 12:37:01.779 [sslvpn:INFO] unknown:0 tty write thread started
20210714 12:37:01.859 [sslvpn:INFO] unknown:0 got peer's ip address
20210714 12:37:02.779 [sslvpn:INFO] unknown:0 ppp interface is up
20210714 12:37:02.780 [sslvpn:INFO] unknown:0 Current dns 0: ...
20210714 12:37:02.781 [sslvpn:INFO] unknown:0 No wins is set currently
20210714 12:37:03.855 [sslvpn:INFO] unknown:0 try to get ppp's ip address ...
20210714 12:37:03.861 [sslvpn:INFO] unknown:0 No split tunnel is specified
20210714 12:37:03.863 [sslvpn:INFO] unknown:0 ppp address: ...
20210714 12:37:03.863 [sslvpn:INFO] unknown:0 sending sslvpn up message to vpn controller. ping server is  allow_save_password:0 allow_keep_alive:0 allow_auto_connect:1
20210714 12:37:03.868 [sslvpn:INFO] unknown:0 launch DNS monitor thread
20210714 12:37:03.868 [sslvpn:INFO] unknown:0 DNS monitor thread started
20210714 12:37:03.876 [sslvpn:INFO] unknown:0 DNS changed
20210714 12:37:03.882 [sslvpn:INFO] unknown:0 Current DNS and DNS got from FGT are same, no needs to reset
20210714 12:43:52.675 [sslvpn:INFO] unknown:0 shuting down the running tunnel
20210714 12:43:52.676 [sslvpn:INFO] unknown:0 the tunnel is shut down
20210714 12:43:52.676 [sslvpn:INFO] unknown:0 reveive SIGUSR1 signal
20210714 12:43:52.676 [sslvpn:INFO] unknown:0 reveive SIGUSR1 signal
20210714 12:43:52.676 [sslvpn:INFO] unknown:0 reveive SIGUSR1 signal
20210714 12:43:52.676 [sslvpn:INFO] unknown:0 reveive SIGUSR1 signal
20210714 12:43:52.676 [sslvpn:INFO] unknown:0 reveive SIGUSR1 signal
20210714 12:43:52.715 [sslvpn:INFO] unknown:0 io loop finished
20210714 12:43:52.736 [sslvpn:INFO] unknown:0 io finished, kill pppd
20210714 12:43:52.768 [sslvpn:INFO] unknown:0 kill_child:7493
20210714 12:43:52.790 [sslvpn:INFO] unknown:0 tunnel shutdown 0
20210714 12:43:52.820 [sslvpn:INFO] unknown:0 sslvpn starts to clean up
20210714 12:43:52.843 [sslvpn:INFO] unknown:0 shuting down the running tunnel
20210714 12:43:52.843 [sslvpn:INFO] unknown:0 the tunnel is shut down
20210714 12:43:52.862 [sslvpn:INFO] unknown:0 sslvpnd terminated
20210715 09:53:01.418 [sslvpn:INFO] unknown:0 current uid: 0
20210715 09:53:01.419 [sslvpn:INFO] unknown:0 get current proxy auto config settings
20210715 09:53:01.423 [sslvpn:INFO] unknown:0 use tty:/dev/ttys000
20210715 09:53:01.425 [sslvpn:INFO] unknown:0 connecting to ...:... - ...
20210715 09:53:01.521 [sslvpn:INFO] unknown:0 [DoLicCheck]...
20210715 09:54:12.548 [sslvpn:INFO] unknown:0 shuting down the running tunnel
20210715 09:54:12.548 [sslvpn:INFO] unknown:0 the tunnel is shut down
20210715 09:54:12.549 [sslvpn:INFO] unknown:0 [DoLicCheck]: GET /remote/licensecheck ... (usr=(null), send 585 of 585 bytes):
GET /remote/licensecheck HTTP/1.1
Host: sslvpn
Cookie: SVPNCOOKIE=+...

View solution in original post

keeno
New Contributor

I had a similar problem with "old" version of FC (Sorry I don't remember which one, since I didn't check before uninstall): every time I tried to connect, it said it couldn't, without any error message. I tried to download version 7 from site but I had another problem (it was "forticlientupdate" app and it gave the message "no updates found" - that's why I uninstalled the old one, to try to avoid this behavior). I came here and I found, in another thread, a hint to download offline installer, so I got version 7.0.0.0022 and it worked like a charm.

Hope this could help

View solution in original post

22 REPLIES 22
AlmightyBob

 if they have offline installers they must have recently added them, all they ever had when this thread started was the “installer” that tried to download the actual (offline) installer but then failed at some point and never actually installed anything.  

 

for all the years our company has used Fortinet as our firewall/vpn this is the only way I’ve ever seen them distribute their software (i.e. the online installer) despite it always failing to install, so if they’ve finally given out an offline version then halle-effing-lujah. I could never understand the whole draconian software distribution model especially when it connects to physical piece of hardware that has to be purchased/licensed anyway… (or maybe it doesn’t I’m not the IT department).

 

 

yetopen

Do you also have the link for the offline VPN only installer? Thanks

PSquires

I used the download link provided by @JamieWhite and it worked like a charm! Super-easy upgrade process and didn't even need to uninstall anything.

 

Background:

I was running FortiClient 5.4.1.514 on my mid-2015 (Intel) MacBook Pro. When I updated to MacOS Monterey, FC suddenly wouldn't connect anymore and returned Error Code -121.

PSquires

I used the download link provided by @JamieWhite and it worked like a charm! Super-easy upgrade process and didn't even need to uninstall anything.

 

Background:

I was running FortiClient 5.4.1.514 on my mid-2015 (Intel) MacBook Pro. When I updated to MacOS Monterey, FC suddenly wouldn't connect anymore and returned Error Code -121.

Miguel1

Thank you very much. This was the fastest way to get this to work

Frank67TS
New Contributor

Mha non so se ti potrà essere utile però io ho risolto installando FortiClinet Vpn aggiornato alla versione per MacOs 7.0.0.0022..una volta scaricata ho spostato come di consueto l'app nella cartella applicazioni.

Inoltre una volta scaricata l'app nella cartella Applicazioni ho aperto il pacchetto contenente l'app con l'applicazione Installer.app...confermato dove chiedeva conferma fino all'avvenuta installazione.

Poi l'applicazione ha funzionato e ha mantenuto la connessione senza problemi.

p.s. ho un Mac mini del 2018 con chip intel.  

Tpoxa

Just installed Monterey, Forti client stopped working.

Just re-installed it from https://www.fortinet.com/support/product-downloads#vpn (7.0.0.22), works with no issues.

lokutus25
New Contributor

Bump.

The downloadable Forticlient VPN 7.0.2 is not working on the latest Mac OS Monterey.

Is this a known issue? Should our customers migrate to Palo Alto?

 

Tpoxa

7.0.1.0060 works for me after I uninstalled and installed it again.

lokutus25

Hi Tpoxa, are you talking about the Forticlient VPN (only) or the full version?

Now seems the full version is working but not the free VPN version.

Thx

 

 

Labels
Top Kudoed Authors