Unable to connect to Minchir over Wireguard - Handshake timeout

[fishbasketballaries 17]

Hello,
For the past week, I've been unable to connect to Minchir over Wireguard. Trying to connect through either ports 1637 and 47107 will result in a handshake timeout. I don't believe my ISP is blocking me since I have no problem connecting to Minchir through OpenVPN using the "1" entry IP address, which makes me wonder if there is a server issue. Could anyone else check if Minchir is connectable over Wireguard?

Someone reported a similar issue here, but unfortunately that thread is a dead end.

I'm using Eddie 2.21.8 on Manjaro Linux. Here is Eddie's system report.

[bavequwa 2]

Hi,

Can confirm,

I 2022.07.16 11:28:52 - Session starting.
I 2022.07.16 11:28:52 - Checking authorization ...
! 2022.07.16 11:28:52 - Connecting to Minchir (Ireland, Dublin)
. 2022.07.16 11:28:52 - Routes, add 146.70.94.2/32 for interface "Wi-Fi 2 (Intel(R) Wi-Fi 6E AX210 160MHz)".
. 2022.07.16 11:28:53 - Routes, add 146.70.94.2/32 for interface "Wi-Fi 2 (Intel(R) Wi-Fi 6E AX210 160MHz)", already exists.
. 2022.07.16 11:28:53 - WireGuard > Setup start
. 2022.07.16 11:28:53 - WireGuard > Setup complete
. 2022.07.16 11:28:53 - WireGuard > Starting WireGuard/0.5.2 (Windows 10.0.22000; amd64)
. 2022.07.16 11:28:53 - WireGuard > Watching network interfaces
. 2022.07.16 11:28:53 - WireGuard > Resolving DNS names
. 2022.07.16 11:28:53 - WireGuard > Creating network adapter
. 2022.07.16 11:28:53 - WireGuard > Using existing driver 0.10
. 2022.07.16 11:28:53 - WireGuard > Creating adapter
. 2022.07.16 11:28:53 - WireGuard > Using WireGuardNT/0.10
. 2022.07.16 11:28:53 - WireGuard > Eddie build 2
. 2022.07.16 11:28:53 - WireGuard > Dropping privileges
. 2022.07.16 11:28:53 - WireGuard > Interface created
. 2022.07.16 11:28:53 - WireGuard > Setup interface
. 2022.07.16 11:28:53 - WireGuard > Setting interface configuration
. 2022.07.16 11:28:53 - WireGuard > Peer 1 created
. 2022.07.16 11:28:53 - WireGuard > Interface up
. 2022.07.16 11:28:53 - WireGuard > Monitoring MTU of default v6 routes
. 2022.07.16 11:28:53 - WireGuard > Setting device v6 addresses
. 2022.07.16 11:28:53 - WireGuard > Monitoring MTU of default v4 routes
. 2022.07.16 11:28:53 - WireGuard > Setting device v4 addresses
. 2022.07.16 11:28:53 - WireGuard > Startup complete
. 2022.07.16 11:28:58 - WireGuard > Handshake for peer 1 (146.70.94.2:1637) did not complete after 5 seconds, retrying (try 2)
. 2022.07.16 11:29:03 - WireGuard > Handshake for peer 1 (146.70.94.2:1637) did not complete after 5 seconds, retrying (try 2)
. 2022.07.16 11:29:08 - WireGuard > Handshake for peer 1 (146.70.94.2:1637) did not complete after 5 seconds, retrying (try 2)
. 2022.07.16 11:29:13 - WireGuard > Handshake for peer 1 (146.70.94.2:1637) did not complete after 5 seconds, retrying (try 3)
. 2022.07.16 11:29:19 - WireGuard > Handshake for peer 1 (146.70.94.2:1637) did not complete after 5 seconds, retrying (try 4)
. 2022.07.16 11:29:24 - WireGuard > Handshake for peer 1 (146.70.94.2:1637) did not complete after 5 seconds, retrying (try 5)
. 2022.07.16 11:29:29 - WireGuard > Handshake for peer 1 (146.70.94.2:1637) did not complete after 5 seconds, retrying (try 6)
. 2022.07.16 11:29:34 - WireGuard > Handshake for peer 1 (146.70.94.2:1637) did not complete after 5 seconds, retrying (try 7)
! 2022.07.16 11:29:37 - Disconnecting
. 2022.07.16 11:29:37 - WireGuard > Stop request received
. 2022.07.16 11:29:37 - WireGuard > Stopping
. 2022.07.16 11:29:38 - WireGuard > Completed

 

[fishbasketballaries 17]

23 hours ago, greyport said:

Hi,

Can confirm

Sounds like it's time to open a ticket, then. Thanks!

[fishbasketballaries 17]

I opened a support request yesterday, but it seems to have vanished.
@Staff Could you check my ticket? It's #166894.

[Staff 10014]

4 hours ago, fishbasketballaries said:

I opened a support request yesterday, but it seems to have vanished.
@Staff Could you check my ticket? It's #166894.

Hello!

We're sorry, we can't find that ticket. We have just read your thread and we will investigate.

Kind regards
 

[Staff 10014]

Hello!

We can't reproduce the problem, our connections via WireGuard to Minchir are fine.

Kind regards
 

[fishbasketballaries 17]

After some more testing, I found that I'm able to connect if I used a new device config. None of my existing device configs were able to connect to Minchir, until I renewed their keys.
So, to fix:

1. Go to your Devices
2. Find your problematic device and click 'Details'
3. Select 'Renew'
4. Log out of Eddie, then log back in, or regenerate your config files with the Config Generator if using WireGuard CLI

@greyport If you don't mind renewing your keys, I'm curious if this works for you too.
 

2 hours ago, Staff said:

We can't reproduce the problem, our connections via WireGuard to Minchir are fine.

Thank you for checking, I apologize for bothering you about this.
 

[bavequwa 2]

@fishbasketballaries I've just tested. After following your steps I was able to connect to Minchir. Wireguard works for me normally on other servers (I mostly use NL nodes) so it's strange that only that server was affected.
It's clear now why Staff was unable to reproduce the issue. Edited ... by greyport

[Staff 10014]

5 hours ago, greyport said:

@fishbasketballaries I've just tested. After following your steps I was able to connect to Minchir. Wireguard works for me normally on other servers (I mostly use NL nodes) so it's strange that only that server was affected.
It's clear now why Staff was unable to reproduce the issue.

Hello!

Since it's clear please feel free to explain, we are very interested in understanding your problem's cause.

Kind regards
 

[bavequwa 2]

Hello,

Well, I meant that it became clear that the problem was user related and not server related. I don't know what was the root cause unfortunately😞 (I only know basics about inner workings of wireguard).

BR