FE6C987894684BECA89087FC87 1 Posted ... (edited) Hello everyone, I'm experiencing frequent disconnects when connecting over wireguard since quite some time. Changing to another server helps, however, the server itself (Menkent in this case) has no issues according to the status page. This happens on multiple devices (linux and macos), the handshake just fails: wireguard: wg2: Sending handshake initiation to peer 1 (213.152.176.140:1637) wireguard: wg2: Sending handshake initiation to peer 1 (213.152.176.140:1637) wireguard: wg2: Sending handshake initiation to peer 1 (213.152.176.140:1637) wireguard: wg2: Handshake for peer 1 (213.152.176.140:1637) did not complete after 5 seconds, retrying (try 2) This goes on for multiple iterations. Sometimes wireguards reconnects faster, sometimes it takes a lot of time. After a few seconds, we're back to: wireguard: wg2: Sending handshake initiation to peer 1 (213.152.176.140:1637) wireguard: wg2: Receiving handshake response from peer 1 (213.152.176.140:1637) [...] wireguard: wg2: Sending keepalive packet to peer 1 (213.152.176.140:1637) wireguard: wg2: Retrying handshake with peer 1 (213.152.176.140:1637) because we stopped hearing back after 15 seconds wireguard: wg2: Sending handshake initiation to peer 1 (213.152.176.140:1637) wireguard: wg2: Handshake for peer 1 (213.152.176.140:1637) did not complete after 5 seconds, retrying (try 2) wireguard: wg2: Sending handshake initiation to peer 1 (213.152.176.140:1637) wireguard: wg2: Handshake for peer 1 (213.152.176.140:1637) did not complete after 5 seconds, retrying (try 3) wireguard: wg2: Sending handshake initiation to peer 1 (213.152.176.140:1637) wireguard: wg2: Sending keepalive packet to peer 1 (213.152.176.140:1637) wireguard: wg2: Retrying handshake with peer 1 (213.152.176.140:1637) because we stopped hearing back after 15 seconds wireguard: wg2: Sending handshake initiation to peer 1 (213.152.176.140:1637) wireguard: wg2: Handshake for peer 1 (213.152.176.140:1637) did not complete after 5 seconds, retrying (try 2) wireguard: wg2: Sending handshake initiation to peer 1 (213.152.176.140:1637) wireguard: wg2: Handshake for peer 1 (213.152.176.140:1637) did not complete after 5 seconds, retrying (try 3) wireguard: wg2: Sending handshake initiation to peer 1 (213.152.176.140:1637) Anyone has an idea why it fails? In case it matters, my connection uses CGNAT. Edit: Forgot to mention that I use the regular Wireguard client, not Eddy or something. Config created via AirVPN website. Edited ... by FE6C987894684BECA89087FC87 Quote Share this post Link to post
Staff 9968 Posted ... @FE6C987894684BECA89087FC87 Hello! Is this WireGuard failure peculiar to Menkent, or are you experiencing it on other servers too? Kind regards Quote Share this post Link to post
FE6C987894684BECA89087FC87 1 Posted ... I can only verify it from one device as changing the endpoint on the other device is quite tedious, but it seems that this happens only with Menkent so far. But I need to test it more in order to make sure. Also, it seems that it only happens with the default port, using port 47107 seems to work flawlessly. I'm going to switch the port and report back about it. 1 Staff reacted to this Quote Share this post Link to post
Staff 9968 Posted ... 21 hours ago, FE6C987894684BECA89087FC87 said: I can only verify it from one device as changing the endpoint on the other device is quite tedious, but it seems that this happens only with Menkent so far. But I need to test it more in order to make sure. Also, it seems that it only happens with the default port, using port 47107 seems to work flawlessly. I'm going to switch the port and report back about it. Hello! We could not detect any problem to port 1637 of Menkent's entry-IP address three, we're sorry. Does the problem still persist? Kind regards Quote Share this post Link to post
mete888 0 Posted ... On 10/3/2024 at 10:24 PM, FE6C987894684BECA89087FC87 said: Changing to another server helps, however, the server itself (Menkent in this case) has no issues according to the status page. I also had issues the last days with Menkent disconnects, and I also use WireGuard. Changed now to a server in germany for the moment... Quote Share this post Link to post
baked-antihero 0 Posted ... I'm also having issues with the Menkent server. I've had a few disconnections over the last few days. Disconnections: 28/10/24 - 13:58(GMT) 27/10/24 - 20:32 27/10/24 - 18:24 27/10/24 - 18:10 26/10/24 - 23:36 26/10/24 - 23:02 26/10/24 - 22:54 Quote Share this post Link to post
Staff 9968 Posted ... Hello! We have WireGuard clients connected to Menkent since July 2024, without a single interruption. We can not confirm any problem on Menkent. Menkent is also on the top user's speed table frequently (right now, while we are writing, it's #1 in the world providing ~1 Gbit/s to a single client). Kind regards Quote Share this post Link to post