WireGuard generates wrong public key
-
i tried to follow this pfSense WireGuard Guide Series 001 - Mullvad Failover but my public key does not match my mullvad/proton public key.
i tried on two separate devices
this post: The WireGuard tunnel public key is derived from the private key. There isn't a compelling reason to allow the user to manually enter it separately, as it only presents an additional opportunity for error/misunderstanding.
what can i do now if i cannot enter the public key manually? -
@sprout0002 If you paste the private key from Mullvad it will generate the same public key.
But I don't think you are setting it up correctly.
To be clear, don't know who or what Mullvad is but wouldn't you want your own public key that would need to be entered on the other side? -
@jarhead in the guide Christian says the public key should match the public key from mullvad vpn
the config file is from proton but i also tried with mullvad... same problem
-
@jarhead said in WireGuard generates wrong public key:
but wouldn't you want your own public key that would need to be entered on the other side?
Goof question, what would be the real benefit of that. You don't use those keys on any other tunnel anyway, so it might be ok to get the whole config from them.
-
-
@bob-dig ok. and when i create a peer (like in the video guide) which public key should i enter?
-
@sprout0002 Theirs. But I don't recommend running pfSense only for a privacy vpn, this is to much complexity.
-
@sprout0002 said in WireGuard generates wrong public key:
@bob-dig ok. and when i create a peer (like in the video guide) which public key should i enter?
You need to put their public key on your peer and they put your public key on their peer. But again, don't know Mullvad so maybe they do something different.
-
@sprout0002 the same thing is occuring with me trying to set it up with NordVPN. Wireguard generates the wrong public key for the private key I'm entering. Did you find a fix or way to enter your public key from proton?