Hi Jan,

So it looks like this is happening to you:

This should not be the behavior, and if it is, you've either found a bug in WireGuard or a bug in your own setup.

1) Are you running the latest snapshot of WireGuard? Which one?

2) "but I don’t know for sure… it seems to be a regression somewhere as I don’t recall to have that problem before…" Can you be more precise?

3) If you are running the latest version, does this patch fix it? http://ix.io/z3d

4) Can you confirm that there exists a route from the server back to the client?

Thanks,

Jason