pi3 vpn server with wireguard

paddy-stone · July 14, 2020

Hi guys I am having problems and can't figure out why.

The problem I am having is not being able to connect after doing everything.

I installed it via pivpn

curl -L https://install.pivpn.io | bash

went through the setup but chose wireguard instead.

I then followed this guide to install duckdns cron updating the ddns https://www.duckdns.org/install.jsp

At the start I had a few errors, but got it working in the end... and that's where I think the problem is, with the errors I previously had.

Because after using

pivpn add

pivpn -qr

and select user, it outputs the qr code. I scan it with my phone wireguard app. But I noticed that in the wireguard settings for the tunnel. It's still using the older domain name that I deleted. I think it might have been from the errors I made previously, but don't know how to fix it apart from starting over again maybe? hoping someone can tell me how to flush the older settings if that's possible?

paddy-stone · July 14, 2020

actually nvm, I'll run pivpn setup again.

paddy-stone · July 14, 2020

Yep, got it working now.

My problem was that I ran the setup the first time with a different domain name... and when I was getting errors for some unknown reason I got frustrated and dumped the domain

I have no idea why I was getting errors though, that's still a mystery... I was inputting/copying the text and changing the relevant parts.

I did come across one really weird one though, I used sudo nano to edit the duck.sh file

echo url="https://www.duckdns.org/update?domains=exampledomain&token=a7c4d0ad-114e-40ef-ba1d-d217904a50f2&ip=" | curl -k -o ~/duckdns/duck.log -K -

but when I checked it again after getting errors it had left out the "echo" part, so I kept getting errors when running ./duck.sh

That was very infuriating, and was the main problem I had, and as I'm not very fluent in linux it was not clear what the problem was. That's why I ended up changing the domain, as I thought that was the problem... and then it caused more problems instead of less.

Anyway, lesson learned! and at least I got a little more useful with linux in general I guess, LOL

So I just ran curl command again to setup the server again. and this time it went without a hitch.

----- I must say that it's actually easier doing a wireguard setup than openvpn, especially as you can just send your clients the qr code if needed. I'm about to do exactly that... they do need to have a phone to read the qr code, and something to read the qr code from though, so not useful for everyone. I can just send a public key if needed though.