PiVPN with Wireguard unreliable when IP changes?

[blimchen]

@Joulinar

the script is designed not to be executed on server side. It should be running on the client to obtain correct DDNS/IP address to be able to connect to server. A typical scenario would be a permanent connection from client to server were server external IP change regular.

Damn, okay. Thanks for pointing that out. I should have read more carefully.

DDNS having the correct external IP address (mxtoolbox says yes) ︎
port forwarding done ︎
correct local device IP (static) ︎
client having the correct settings (probably) ︎
pass pivpn debug (ok) ︎

I managed to resolve the situation. Simply rebooted the router, the iPhone, and the RaspberryPi. I guess there’s no way to run a sh script on an iPad or iPhone though.

It’s either the client side (i.e. iDevice) or some obscure configuration that makes PiVPN/Wireguard unstable for me. It mostly works, however from time to time it simply stops functionning. It’s fickle!
The client device mostly shows up as currently connected, when I then run pivpn -c, but I can’t connect to my local network.

[Joulinar]

@blimchen

I guess there’s no way to run a sh script on an iPad or iPhone though.

I would wonder if this is possible

But usually, you don’t keep the VPN active all time on your mobile device. Isn’t it? And while switching VPN active, the client will receive correct IP/DDNS. The script makes sense on systems keeping a VPN connection active for days, weeks aso.

[blimchen]

@Joulinar

Isn’t it? And while switching VPN active, the client will receive correct IP/DDNS. The script makes sense on systems keeping a VPN connection active for days, weeks aso.

No, I just switch it sporadically on. Thanks for clearing that up.