You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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
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?
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.
The text was updated successfully, but these errors were encountered: