Comments
-
Nervermind, i found the solution. Logically, 2nd domain cannot use the same $uri as the main domain. Documentation just could be clearer and states that you have to do the same powershell actions for the 2nd domain, and add the " ?seconddomain.com" in the $uri parameter. BV
-
Hey, Thanks for answer, i got it working. Had a (crappy) Symantec Endpoint Protection who was the root of the problem. Fixed it :) Thanks everyone for answers. BV
-
Hi again, So i followed the documentation here : https://www.watchguard.com/help/docs/help-center/en-US/Content/Integration-Guides/AuthPoint/firebox-ikev2-vpn-radius_authpoint.html Firebox up to date Authpoint Gateway and NPS on same server (NPS listening on different port then 1812). Authpoint configured with MS-Chapv2..…
-
In France for exemple, a bunch of IPs owned by OVH are considered as botnet members. BV
-
I had a conversation yesterday with a Watchguard member.. It seems that there was a problem of botnet identification ... I had myself the same problem with OVH. Just put the FQDN in exception to fix the problem of you website. Botnet ID problem is on exam as far as i know.