Hi all
I’m trying to get a normal windows VPN IKEv2 connection configured with the ikev2/openvpn credentials from my proton account page and used one of the free NL server IPs (169.150.196.145) that I got from the openvpn configuration file
Unfortunately I get a Policy match error.
As the original article which is linked “everywhere” https://protonvpn.com/support/windows-10-ikev2-vpn-setup/ now redirects to a windows and wireguard setup, I had to take the waybackmachine route.
I’ve added the root ca cert that is linked in the “old” article and used the username/password from my account page.
unfortunately i still get the same error
does anyone have any hint how to fix that? or have another (maybe DNS name) of the free NL servers
They removed IKEv2 support IINM.
We plan to completely discontinue IKEv2 support in the future. With that in mind, we suggest you try manually configuring WireGuard (https://protonvpn.com/support/wireguard-manual-windows) or OpenVPN (https://protonvpn.com/support/openvpn-windows-setup) instead.
you tried the reg fix (NegotiateDH2048_AES256) for policy match error?
I was looking at the 21-Mar-2023 version.
ok? because I can still connect with the window setting stuff after the fix …
but Either I’m again too dumb or split tunneling configuration for a specific app does not work …
I tried to enable it via
Set-VpnConnection -Name “VPNNAME” -SplitTunneling $True
Add-VpnConnectionTriggerApplication -Name “VPNNAME” -ApplicationID “Applicationexecutable”
it start the vpn as soon as the application is started … but it seems that the traffic for that app is not going through the tunnel … just tried chrome to test things out and if I check my external IP via whatismyipaddress.com in chrome I still get my “normal” ip
oh my dear … after re-checking the waybackmachine on that date and looking for the mentioned fix, I realised that the other tab (that I had still open) had not loaded completely and just ended after the credentials (step 3) where you have to click connect … the page wasn’t loaded … feeling dumb now …
The fix worked … 
nevertheless still strange that the link to that article got removed and pointing to wireshark now.
nevertheless still strange that the link to that article got removed and pointing to wireshark now.