From: Nazar Mokrynskyi <nazar@mokrynskyi.com>
To: wireguard@lists.zx2c4.com
Subject: Re: Android can't complete handshake
Date: Mon, 18 Mar 2024 21:36:37 +0200 [thread overview]
Message-ID: <d5d152e4-0acd-43ea-b89a-ffa63fc1fd2f@mokrynskyi.com> (raw)
In-Reply-To: <1ac814fd-85ba-4b73-97b2-b13ddde13873@mokrynskyi.com>
Still happening, hard to believe I'm the only one.
Anything else I can provide to help debug this?
Sincerely, Nazar Mokrynskyi
github.com/nazar-pc
01.11.23 03:23, Nazar Mokrynskyi:
> Basically every day I have the following in logs:
>
>> 10-16 00:46:05.380 5200 5568 D WireGuard/GoBackend/xyz: peer(8MoP…XPVc) - Handshake did not complete after 5 seconds, retrying (try 2)
>> 10-16 00:46:05.381 5200 5568 D WireGuard/GoBackend/xyz: peer(8MoP…XPVc) - Sending handshake initiation
>> 10-16 00:46:10.468 5200 5678 D WireGuard/GoBackend/xyz: peer(8MoP…XPVc) - Handshake did not complete after 5 seconds, retrying (try 3)
>> 10-16 00:46:10.469 5200 5678 D WireGuard/GoBackend/xyz: peer(8MoP…XPVc) - Sending handshake initiation
> This is happening on Android 14 when connected to Wi-Fi.
>
> It is definitely not a loss of Wi-Fi or Internet connectivity, I turn off and immediately turn on the VPN connection and it connects instantly and successfully, it is just those retries that are not succeeding.
>
> Is this a know issue, maybe there is a workaround?
>
> I have seen similar reports online that seem to be related to network connectivity, which is not the case here or else reconnection would fail too.
>
prev parent reply other threads:[~2024-03-18 19:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-01 1:23 Android can't complete handshake Nazar Mokrynskyi
2024-03-18 19:36 ` Nazar Mokrynskyi [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=d5d152e4-0acd-43ea-b89a-ffa63fc1fd2f@mokrynskyi.com \
--to=nazar@mokrynskyi.com \
--cc=wireguard@lists.zx2c4.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).