I hope, you have opened a support case with tech support, so they can have a look at your configuration.ĭid you make a backup before upgrading? Usually the upgrade procedure would offer you to make a backup.

Unfortunately I have no idea what could have gone wrong in that part of your effort. Removing/reconfiguring IKEv2 and redeploying client configurations should reestablish VPN connectivity for your clients - in theory. I guess, that the large version jump has upgraded the certificates, what broke the connectivity for your clients. Having remote VOIP issues and occasional data not laying down in Filemaker database. So now I'm stuck and unsure what to do next.Īny help is appreciated, currently I have 30+ users remoting in via WG Mobile VPN w SSL app which isn't good, just good enough. Now when I get to the end of the wizard it's telling me 'Muvpn-ipsec 'WG IKEv2 MVPN' is already in use' So I tried disabling IKEv2 in Fireware Web GUI and re-launching the wizard. Then re-adding it from a newly downloaded 'WG IKEv2.mobileconfig' from the Firebox.

I tried removing the 'WG IKEv2' profile on my Macbook's System Prefs > Profiles and then removed the 'WG IKEv2' setup under System Prefs > Network. Fireware Web GUI traffic monitor would show something in the likes of 'ike cert chain failed'. When attempting to connect from a Macbook, on the laptop it would say user authentication failed. I ended up updating the M300 Firebox's OS from 11.0.x (can't remember the exact sub-version) to the latest version, 12.5.3. It went fine and worked from a remote Macbook. Beginning of this week I set up Mobile VPN via IKEv2 using the Fireware Web GUI's wizard.

Watchguard ssl vpn for mac