User has a mac with the correct vpn client, 12.7.2. Gets error message “Connection failed, please check your server IP or network.” Server IP is correct. Credentials are correct. From a windows PC with same client, 12.7.2, same credentials it works fine. I’m not a mac expert and don’t know what to do here. Why is this not working on a mac?
Copied from a WG community: https://community.watchguard.com/watchguard-community/discussion/2855/mobile-vpn-with-ssl-12-7-2-for-macos-ventura
I just upgraded to Ventura myself and realized that Watchguard Mobile VPN with SSL would no longer work. I am not 100% sure how I did it, but here is a close list that fixed it for me.
1 - ran the Mobile VPN with SSL installer again(not sure if this is necessary)
2 - launched and attempted to connect to my VPN.
3 - opened MacOS System Settings and then went into the new Privacy & Security section. In there toward the bottom or in there and in extensions it showed that there was a Watchguard Extension being blocked. I selected to allow it and put in my OS password when prompted to update settings. At that point I rebooted. Then I got a certificate dialog when attempting to connect to the VPN that allowed me to view the cert, decline, or continue. I selected to view the certificate and selected the Always Trust checkbox at the top section of that window. I think I may have rebooted again, but then it connected to my SSL VPN normally using the Watchguard Mobile VPN with SSL application on MacOS Ventura.
Hope this helps someone. It’s working for me again.
Is there anything on macs that would interfere/block the vpn client?
use Tunnelblick Downloads - Tunnelblick | Free open source OpenVPN VPN client server software for macOS
hola, me me esta pasando en mi Mac m1 con sequoia 15.1, no me puedo conectarme, y ya no se donde mas ver si esta bloqueada la aplicación, ayuda plis
Hi,
I’ve found the solution for MacOS sequoia 15.1. and Watchguard Mobile VPN with SSL.
1 - Open MacOS System Settings and then went into the new Privacy & Security section. In there toward the bottom or in there and in extensions it showed that there was a Watchguard Extension being blocked. I selected to allow it and put in my OS password when prompted to update settings. Then reboot the Mac.
2 - You need to open Keychain and select the Certificates tab. Then find the certificate named “Fireware web CA”, right-click on the icon > read information > unfold the Trust tab and select “always approve”.
3 - Then reboot the Mac and it should work!
Do you know where these extensions are located in the later versions of OSx?
I’m not seeing the Watchguard extension from showing up so it can be unblocked. Previously I was able to do this while on Ventura, but on Sequoia I’m not seeing this. Are you able to provide any additional information to help fix this?
Hi,
It’s not an extension : it’s a Certificate you must find
You need to open Keychain access in the utilities. Then select the Certificates tab. Find the certificate named “Fireware web CA”, right-click on the icon > read information > unfold the Trust tab and select “always approve”.
Then reboot the Mac and it should work!
Having this exact same issue and can’t find this certificate - do you know if it might be called something else? Have reached out to Watchguard support to ask the same thing.
inement du ancienne version , là cela fonctionne j’ai bien le certificat à autoriser.
Bonjour, j’ai le même problème et j’ai trouve la solution ! il faut en fait que tu télécharge un ancien client. Moi je l’ai télécharge depuis mon wathguard (ip et port :4443) et la cela me demande bien d’autoriser le certificat.
Ich hatte die Version 12.10.4 von WatchGuard Mobile VPN. Bei mir lag das Problem ebenfalls am Zertifikat „Fireware Web CA“, das nicht vorhanden war. Ich habe es von meinem alten Mac kopiert und in den Schlüsselbund meines neuen Macs unter „Zertifikate“ eingefügt. Nachdem ich das Zertifikat auf „Vertrauen“ gesetzt habe, funktioniert es jetzt. Möglicherweise hätte es auch funktioniert, wenn ich eine ältere Version von WatchGuard Mobile VPN installiert hätte, um das Zertifikat zu erhalten, aber das habe ich nicht ausprobiert. Hauptsache, es funktioniert jetzt.