ProtonVPN directions for configuring WireGuard on a Mikrotik router include statement that "Your WireGuard private key ... can be found by opening the configuration file ..." downloaded from the ProtonVPN site. However, when I look at the WireGuard config file that I downloaded from the ProtonVPN site, the config file does not include an actual private key string. Instead the ProtonVPN WireGuard config file includes what looks like a masked string "*****" [See below]. So the question for me is how I determine the private key string that I should be inputting via CLI when configuring a Mikrotik router to use the ProtonVPN Wireguard protocol. Helpful tips and suggestions much appreciated.
For reference, I have attached a copy of the ProtonVPN directions for configuring WireGuard on a Mikrotik router (or at least what think are the correct directions). And below is a copy of the related config file that I downloaded from the ProtonVPN website that includes the public key to use, but not the private key.
[Interface]
Key for Proton_Wireguard_CA1
Bouncing = 3
NetShield = 1
Moderate NAT = off
NAT-PMP (Port Forwarding) = off
VPN Accelerator = on
PrivateKey = *****
Address = 10.2.0.2/32
DNS = 10.2.0.1
Well I solved the question. Root cause was that I didn’t wait long enough before downloading the ProtonVPN WireGuard config file. So my learning was to give the ProtonVPN website 5+ seconds to finish creating the config file before downloading it.
I confirmed this by re-performing the process of creating a config file on the ProtonVPN website, and now have a new config file that includes a private key string. So all good until next bump in the road/process. Thx.
Note1: if you don’t want the subnet (or entire bridge) to use local WAN if proton vpn is not working then change action to action=lookup-only-in-table
Note2. If subnet A needs to reach other subnets behind router then add FIRST, dst0-address routing rules to prevent such traffic from being forced out tunnel
I followed you instruction and everything work on my mAP Lite.
However, when I try to connect to the router with WinBox using its IP address, the connection fails, whereas if I use the router's MAC address, I can connect.