Can I setup my Windows client machine using the old method now? Without WireGuard.

[waltirus]

Please, help me to get clear if I can still rely on Algo as my vpn server, since WireGuard is not working any more with it - it looks like the authorities are blocking the protocol of WireGuard -it's not working with new IP I got from my cloud provider too.. So, my idea is to try the other way , other protocol (IPSec, I guess) , there is a chance it might be working. I don't see the file ps1 in the config folder any more. Can I setup my Windows client machine without it? Just using p12 password file..? I'll appreciate your help very much. Thank you.

[waltirus]

I have found the description of manual setup of windows client machine but I have received error messages (highlighted in red fonts) on the following commands: Import-PfxCertificate -FilePath $UserP12Path -CertStoreLocation Cert:\LocalMachine\My -Password $p12Pass The error response was : Import-PfxCertificate : Не удалось найти файл PFX. (Could not find the PFX file: translated fr Russian) строка:1 знак:1

• Import-PfxCertificate -FilePath $UserP12Path -CertStoreLocation Cert: ...

•   + CategoryInfo          : NotSpecified: (:) [Import-PfxCertificate], FileNotFoundException
    + FullyQualifiedErrorId : System.IO.FileNotFoundException,Microsoft.CertificateServices.Commands.ImportPfxCertificate
  
  

The following command also caused an error message: Import-Certificate -FilePath $CaCertPath -CertStoreLocation Cert:\LocalMachine\Root Responded: Import-Certificate : Не удалось найти файл сертификата (Could not find the file of certificate: translated). строка:1 знак:1

• Import-Certificate -FilePath $CaCertPath -CertStoreLocation Cert:\Loc ...

At the attempt to connect via created VPN connection it said : Error of Group Policy compatibility. Could any one help me to understand how to correct the manual script to avoid these messages? Why could not it find that PFX file? And where are the certificate file store in Windows 10? May be the path to them should be corrected?

[dguido]

Hi @waltirus,

Thank you for reporting this issue with IKEv2 on Windows. IKEv2 support for Windows was removed from Algo in version 1.1 (July 31, 2019) as documented in our changelog.

For Windows clients, we now recommend using WireGuard, which provides:

• Better performance
• Easier configuration
• More reliable connections
• Active development and support

You can find instructions for setting up WireGuard on Windows at: https://github.com/trailofbits/algo#windows

Since IKEv2 for Windows is no longer supported, I'm closing this issue. Please use WireGuard for Windows clients going forward.

Thank you for using Algo!