Replies: 1 comment
-
|
Some more info I suspect manually creating the tunnel on my iPhone would work too, I will try when I have a chance - it's a pain to get the keys to the iPhone or type them in manually. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Has anyone used genkey to generate public and private keys for the clients? I created both server and peer key pairs and incorporated them into the Wireguard configuration. When I used the qr code to create a tunnel on my iPhone, it said invalid qr code and did not create the tunnel.
So I took some steps and incorporated the keys one by one.
In between each of the above steps I stopped wireguard, deleted the peer files and directory, made the config changes, then started wireguard. A new directory with peer files appeared, so it would seem addon-wireguard regenerates them if they are not there. (would be nice to add this to the documentation)
Here's how I tested for successful connection:
I run Home Assistant in IOTstack - which results in wireguard running in a docker container. I use portainer to open a console in the wireguard container and run wg show. When successful tunnel is established it will show the ip of the client and #bytes sent/received. I also run checkip.dyndns.com from the iPhone and confirm a successful tunnel when it displays the WAN IP of the network in which the wireguard server is running.
Beta Was this translation helpful? Give feedback.
All reactions