Reattempt failed WireGuard connections

[ignoramous]

A user writes,

wireguard connection can give an error (Listening port already active or something like that) and turn itself off but not automatically resume when the connection stabilizes.

On Rethink tunnel restarts (on drastic network configuration changes), WireGuard proxy re-attempts binding on to a local port which, oftentimes, may not be available. Perhaps, a retry is of the order before giving up (since giving up means, the tunnel is essentially disabled, potentially leaking connections outside of the proxy. At least until #976 is implemented).

In general, it'd be nice to avoid hitting the "port in use" error less often...

[ignoramous]

Related:

• WireGuard with Dynamic DNS #1013

[ignoramous]

Fixed for v055a (hopefully it is ready to go in 2 days).