ANSWERED Can't connect via WireGuard anymore

Greyzy

Hi,
I use WireGuard (not Eddie) to connect. This worked fine, but today something is wrong:
- I can activate the tunnel, but when I try to go to a webpage (e.g. google.com) my browser (Firefox) can't find the webpage. I suspect the DNS resolution is not working, but I am no expert on this. The DNS server in the script is: 10.128.0.1 (that's the setting when I downloaded the file)
- Here's a part of the log file:

2024-06-21 14:09:01.234: [MGR] Starting at boot WireGuard/0.5.3 (Windows 6.1.7601; amd64)
2024-06-21 14:09:01.290: [MGR] Starting UI process for user ‘Thommi@Blechdose-II’ for session 1
2024-06-21 14:11:48.837: [TUN] [AirVPN_1_Germany] Starting at boot WireGuard/0.5.3 (Windows 6.1.7601; amd64)
2024-06-21 14:11:48.838: [TUN] [AirVPN_1_Germany] Watching network interfaces
2024-06-21 14:11:48.848: [TUN] [AirVPN_1_Germany] Resolving DNS names
2024-06-21 14:11:49.868: [TUN] [AirVPN_1_Germany] Creating network adapter
2024-06-21 14:11:50.502: [TUN] [AirVPN_1_Germany] Using existing driver 0.10
2024-06-21 14:11:51.030: [TUN] [AirVPN_1_Germany] Creating adapter
2024-06-21 14:11:53.783: [TUN] [AirVPN_1_Germany] Using WireGuardNT/0.10
2024-06-21 14:11:53.783: [TUN] [AirVPN_1_Germany] Enabling firewall rules
2024-06-21 14:11:53.531: [TUN] [AirVPN_1_Germany] Interface created
2024-06-21 14:11:53.803: [TUN] [AirVPN_1_Germany] Dropping privileges
2024-06-21 14:11:53.803: [TUN] [AirVPN_1_Germany] Setting interface configuration
2024-06-21 14:11:53.803: [TUN] [AirVPN_1_Germany] Peer 1 created
2024-06-21 14:11:53.803: [TUN] [AirVPN_1_Germany] Setting device v6 addresses
2024-06-21 14:11:53.803: [TUN] [AirVPN_1_Germany] Sending keepalive packet to peer 1 (127.124.0.1:1637)
2024-06-21 14:11:53.803: [TUN] [AirVPN_1_Germany] Sending handshake initiation to peer 1 (127.124.0.1:1637)
2024-06-21 14:11:53.803: [TUN] [AirVPN_1_Germany] Interface up
2024-06-21 14:11:54.970: [TUN] [AirVPN_1_Germany] Setting device v4 addresses
2024-06-21 14:11:55.207: [TUN] [AirVPN_1_Germany] Skipping execution of script, because dangerous script execution is safely disabled: `iptables -I OUTPUT ! -o %i -m mark ! --mark $(wg show %i fwmark) -m addrtype ! --dst-type LOCAL -j REJECT && ip6tables -I OUTPUT ! -o %i -m mark ! --mark $(wg show %i fwmark) -m addrtype ! --dst-type LOCAL -j REJECT`
2024-06-21 14:11:55.207: [TUN] [AirVPN_1_Germany] Startup complete
2024-06-21 14:11:58.809: [TUN] [AirVPN_1_Germany] Sending handshake initiation to peer 1 (127.124.0.1:1637)
2024-06-21 14:12:03.829: [TUN] [AirVPN_1_Germany] Sending handshake initiation to peer 1 (127.124.0.1:1637)
2024-06-21 14:12:08.890: [TUN] [AirVPN_1_Germany] Sending handshake initiation to peer 1 (127.124.0.1:1637)
2024-06-21 14:12:14.142: [TUN] [AirVPN_1_Germany] Handshake for peer 1 (127.124.0.1:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-21 14:12:14.142: [TUN] [AirVPN_1_Germany] Sending handshake initiation to peer 1 (127.124.0.1:1637)
2024-06-21 14:12:19.392: [TUN] [AirVPN_1_Germany] Handshake for peer 1 (127.124.0.1:1637) did not complete after 5 seconds, retrying (try 2)


this repeats until eventually it goes on with:


2024-06-21 14:15:53.158: [TUN] [AirVPN_1_Germany] Skipping execution of script, because dangerous script execution is safely disabled: `iptables -D OUTPUT ! -o %i -m mark ! --mark $(wg show  %i fwmark) -m addrtype ! --dst-type LOCAL -j REJECT && ip6tables -D OUTPUT ! -o %i -m mark ! --mark $(wg show  %i fwmark) -m addrtype ! --dst-type LOCAL -j REJECT`
2024-06-21 14:15:53.160: [MGR] [AirVPN_1_Germany] Tunnel service tracker finished
2024-06-21 14:15:57.478: [TUN] [AirVPN_1_Germany] Shutting down

Please advise how to fix this!

Thanks,
Tom

Greyzy

I just created a fresh config file for WireGuard. Here's the log when I tried it (unsuccessfully):

2024-06-21 15:11:10.122: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Starting WireGuard/0.5.3 (Windows 6.1.7601; amd64)
2024-06-21 15:11:10.122: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Watching network interfaces
2024-06-21 15:11:10.125: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Resolving DNS names
2024-06-21 15:11:11.143: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Creating network adapter
2024-06-21 15:11:11.384: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Using existing driver 0.10
2024-06-21 15:11:11.739: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Creating adapter
2024-06-21 15:11:13.011: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Using WireGuardNT/0.10
2024-06-21 15:11:13.058: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Enabling firewall rules
2024-06-21 15:11:12.724: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Interface created
2024-06-21 15:11:13.091: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Dropping privileges
2024-06-21 15:11:13.094: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Setting interface configuration
2024-06-21 15:11:13.095: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Peer 1 created
2024-06-21 15:11:13.095: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Setting device v4 addresses
2024-06-21 15:11:13.095: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending keepalive packet to peer 1 (127.124.0.3:1637)
2024-06-21 15:11:13.095: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:11:13.095: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Interface up
2024-06-21 15:11:13.807: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Setting device v6 addresses
2024-06-21 15:11:14.288: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Startup complete
2024-06-21 15:11:18.372: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:11:23.390: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:11:28.469: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:11:33.644: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.124.0.3:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-21 15:11:33.644: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:11:38.895: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.124.0.3:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-21 15:11:38.895: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:11:44.145: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.124.0.3:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-21 15:11:44.145: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:11:49.328: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:11:54.484: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:11:59.515: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:12:04.574: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.124.0.3:1637)
2024-06-21 15:12:07.918: [MGR] [AirVPN_Germany_UDP-1637-Entry3] Tunnel service tracker finished
2024-06-21 15:12:10.129: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Shutting down

invok3r

That peer address does not look correct. I'd suggest you create the config and turn on the "advanced" mode. after that On the right hand side you'll see a new block and turn on resolved hosts. That should solve your problems if not then manually find the peer address of the server and use it in your config in the PEER section.

go558a83nk

7 hours ago, invok3r said:

That peer address does not look correct. I'd suggest you create the config and turn on the "advanced" mode. after that On the right hand side you'll see a new block and turn on resolved hosts. That should solve your problems if not then manually find the peer address of the server and use it in your config in the PEER section.

I was thinking the same thing the day this was posted but didn't reply because I figured Staff would handle it or confirm the IP address was somehow correct. If the system is having to resolve the domain of the server and is getting 127.124.0.3 as the answer would that imply that there's some DNS poisoning happening by whatever DNS is being used by the OP prior to connecting to VPN?

Greyzy

@invok3r @go558a83nk
Thanks guys,

as @invok3r suggested I recreated the config files (for several countries) in the "advanced" mode and switched to resolved hosts. I compared these files to the ones I used before. All that needed to be changed was the one line with the setting "Endpoint = xxx".

I reimported the config files into the WireGuard app and now it works fine again.

Thanks again for your help!!!
Tom

go558a83nk

15 minutes ago, Greyzy said:

@invok3r @go558a83nk
Thanks guys,

as @invok3r suggested I recreated the config files (for several countries) in the "advanced" mode and switched to resolved hosts. I compared these files to the ones I used before. All that needed to be changed was the one line with the setting "Endpoint = xxx".

I reimported the config files into the WireGuard app and now it works fine again.

Thanks again for your help!!!
Tom

Glad it's fixed. But what was the endpoint in the old configs?

Greyzy

5 minutes ago, go558a83nk said:

Glad it's fixed. But what was the endpoint in the old configs?

The old files were created by NOT using the advanced mode (equal to using the advanced mode, but have "resolved hosts" turned OFF). This would give you entries like:

Endpoint = de3.vpn.airdns.org:1637

instead of

Endpoint = 141.98.102.245:1637

Similarly for other countries, like Netherlands:

Endpoint = nl3.vpn.airdns.org:1637

Does that answer your question?

go558a83nk

2 minutes ago, Greyzy said:
The old files were created by NOT using the advanced mode (equal to using the advanced mode, but have "resolved hosts" turned OFF). This would give you entries like:
Endpoint = de3.vpn.airdns.org:1637
instead of
Endpoint = 141.98.102.245:1637
Similarly for other countries, like Netherlands:
Endpoint = nl3.vpn.airdns.org:1637
Does that answer your question?

Yes, that's what I'm wondering. So I'm concerned that your DNS lookups were/are poisoned and that's why you couldn't connect. Your system was resolving

de3.vpn.airdns.org

to

127.124.0.3

according to the log. That's totally wrong.

You definitely need a VPN to avoid whatever DNS your system was/is using but also change to a trusted, secure DNS for when you aren't using VPN.

Greyzy

OK, I believe I understand what you are saying. Thanks for letting me know!

Is there a way to check/fix if my DNS lookups are poisoned? I don't even really know how that "poisoning" works. Might there be a virus running on my system?

I attached a screenshot montage of the LAN settings for the "standard" internet connection without VPN and also when I use WireGuard. Does that help? Is there some other place I need to look?

I'm grateful for any help you can provide!
Tom

Greyzy

@Staff Could you please give me some advice on the issue that @go558a83nk has identified above: the DNS lookup of the peer address was wrong. He suggested there might be DNS poisoning going on.

Could you please explain how to do the following:
a) verify the reason for the faulty DNS lookup
b) check if anything is wrong on my PC (virus, settings, cache etc.)
c) fix whatever the cause is (and measures to prevent similar problems in the future)

I did a bit of research on DNS lookup poisoning, but didn't quite understand most of it. It appears that clearing some cache and changing DNS server settings might be helpful, but I am not sure what DNS servers to use and also on what level the setting should be done (e.g. in the individual connection settings on each individual PC in my network or in the router that runs my network).

Please advise! Thanks a lot!
Tom

go558a83nk

So the question I have is what DNS are you using when the VPN isn't "on"? With VPN off, go to ipleak.net and check.

Greyzy

@go558a83nkI am not sure where exactly to find the info you want me to check, so I'll post a screenshot (I'll redact my IP for privacy reasons).

I'll also post the info from this website https://www.top10vpn.com/de/tools/was-ist-mein-dns-server/ that gives info on the DNS servers used. Just to contrast the results I'll also add the results from these two webpages for a second PC (WIN-10) that is attached to the exact same router in the same way (LAN). The PC I use AirVPN on is the WIN-7 PC (results of course with VPN turned off). In the adapter settings for the WIN-7 PC I removed the checkmark from IPv6, so it only uses IPv4.

Results from https://www.top10vpn.com/de/tools/was-ist-mein-dns-server/

========
WIN-7 PC

Country   ISP   DNS-Server
DE   VODANET International IP-Backbone of Vodafone   80.69.97.150
DE   VODANET International IP-Backbone of Vodafone   2a02:908:2:110b::30

========
WIN-10 PC

Country   ISP   DNS-Server
US   CLOUDFLARENET - Cloudflare, Inc.   162.158.85.77
US   CLOUDFLARENET - Cloudflare, Inc.   162.158.109.148
US   CLOUDFLARENET - Cloudflare, Inc.   162.158.85.47
US   CLOUDFLARENET - Cloudflare, Inc.   162.158.109.146
US   CLOUDFLARENET - Cloudflare, Inc.   172.70.245.138
US   CLOUDFLARENET - Cloudflare, Inc.   162.158.93.155
US   CLOUDFLARENET - Cloudflare, Inc.   172.70.245.141
US   CLOUDFLARENET - Cloudflare, Inc.   2400:cb00:71:1024::a29e:5514
                       2400:cb00:696:1024::ac44:c31a
US   CLOUDFLARENET - Cloudflare, Inc.   2400:cb00:472:1024::ac46:f9ca
US   CLOUDFLARENET - Cloudflare, Inc.   2400:cb00:470:1024::ac46:f19e
                       2400:cb00:637:1024::a29e:6d92

========

Let me know, if you need any other info (please be as specific as possible on how to obtain it).

Cheers,
Tom

Staff

11 hours ago, Greyzy said:

@Staff Could you please give me some advice on the issue that @go558a83nk has identified above: the DNS lookup of the peer address was wrong. He suggested there might be DNS poisoning going on.

Hello!

Names resolution order in Windows default settings is:

hosts file
DNS
NetBIOS

DNS is queried if no match is found on the hosts file. hosts file is typically edited by filter programs to force some domain names to resolve into non routable IP addresses, as it happened in your case with our FQDNs. Just to make two examples, to block resolution of ad related names, or prevent access to dangerous services. Please check your hosts file and also make sure that your machine queries a neutral DNS (we recommend Quad9, 9.9.9.9, for commitment to privacy and neutrality).

Kind regards

Greyzy

This is the content of the hosts file on the WIN-7 PC:

# Copyright (c) 1993-2009 Microsoft Corp.
#
# This is a sample HOSTS file used by Microsoft TCP/IP for Windows.
# This file contains the mappings of IP addresses to host names. Each
# entry should be kept on an individual line. The IP address should
# be placed in the first column followed by the corresponding host name.
# The IP address and the host name should be separated by at least one
# space.
# Additionally, comments (such as these) may be inserted on individual
# lines or following the machine name denoted by a '#' symbol.
# For example:
#      102.54.94.97     rhino.acme.com          # source server
#       38.25.63.10     x.acme.com              # x client host

# localhost name resolution is handled within DNS itself.
#	127.0.0.1       localhost
#	::1             localhost
#	85.17.207.151	airvpn.org		# server for AirVPN homepage
127.0.0.1 activation.acronis.com web-api-tih.acronis.com
127.0.0.1 lmlicenses.wip4.adobe.com
127.0.0.1 lm.licenses.adobe.com
127.0.0.1 na1r.services.adobe.com
127.0.0.1 hlrcv.stage.adobe.com
127.0.0.1 practivate.adobe.com
127.0.0.1 activate.adobe.com
127.0.0.1 genuine.adobe.com
127.0.0.1 prod.adobegenuine.com
94.242.230.4	lu1-ovpn-tcp.pointtoserver.com
45.74.6.2	sx400411-ikev.pointtoserver.com

Is there anything wrong?

Staff

10 minutes ago, Greyzy said:

Is there anything wrong?

Hello!

Nothing related to *.airdns.org, therefore the problem is not there. However, your hosts file has been edited to prevent license verification by Adobe servers.

Kind regards

Greyzy

1 minute ago, Staff said:

Hello!

Nothing related to *.airdns.org, therefore the problem is not there.

Kind regards

Thanks! Good to know, but where else should I look? Did you see what I posted above regarding the DNS info? Anything out of the ordinary there?

Staff

3 minutes ago, Greyzy said:

but where else should I look?

Hello!

Change DNS settings, have your system query only Quad9 and OpenNIC.

Kind regards

Greyzy

4 minutes ago, Staff said:

Hello!

Change DNS settings, have your system query only Quad9 and OpenNIC.

Kind regards

Where do you recommend I change the settings? On each PC or on the router? Where on the PC should I change the setting: if I do it for each adapter separately, how do I treat the adapter used by WireGuard?

Also: what is the setting for OpenNIC (Quad9 is 9.9.9.9 as you wrote above)?

Staff

2 minutes ago, Greyzy said:

Where do you recommend I change the settings? On each PC or on the router?

Hello!

On each PC and on the router. PC DNS settings take precedence, but if a PC queries also the router (even if only as a fallback) then it's essential that the router DNS is not poisoned. So change them all.

3 minutes ago, Greyzy said:

what is the setting for OpenNIC

Please check https://www.opennic.org

Kind regards

Greyzy

1 hour ago, Staff said:

Hello!

On each PC and on the router. PC DNS settings take precedence, but if a PC queries also the router (even if only as a fallback) then it's essential that the router DNS is not poisoned. So change them all.

Please check https://www.opennic.org

Kind regards

Thanks, I'll do as you suggested. Unfortunately I get this when I try the link you posted:

Staff

5 minutes ago, Greyzy said:

Unfortunately I get this when I try the link you posted:

Hello!

Hopefully nothing serious has happened and let's hope that their site will be up again soon.

Kind regards

Greyzy

53 minutes ago, Staff said:

Hello!

Hopefully nothing serious has happened and let's hope that their site will be up again soon.

Kind regards

I got the info some other way...

So I changed the settings in the adapters on the PC (not on the router) with Quad9 as primary and OpenNIC as secondary DNS servers.
I then created two config files for the German AirVPN servers (attached). The only difference is, that one shows the peer address as

Endpoint = de3.vpn.airdns.org:1637

and the other as

Endpoint = 178.162.212.216:1637

Result: the first connection does NOT work, the second does.

Attached are screenshots of the results from ipleak.net, the adapter settings created by these files (appear to be identical) and the two config files.

What's the problem??? Why does one work and the other doesn't???

AirVPN_Germany_UDP-1637-DNS.conf AirVPN_Germany_UDP-1637-noDNS.conf

Staff

4 hours ago, Greyzy said:

What's the problem??? Why does one work and the other doesn't???

Hello!

Same as before we guess, although you did not send new log: name resolution problem. Please re-check DNS settings and test resolution with "nslookup" command.

Quote

I changed the settings in the adapters on the PC (not on the router)

According to the previous recommendations you must set DNS properly on the router too.

Kind regards

Greyzy

@Staff I now have set the DNS server on the router as recommended to Quad9 and OpenNIC.
I am not sure how you suggest I use "nslookup" (I am no expert in this so a bit more details on what to do for troubleshooting is appreciated!). Here's what I tried: I used the command to look up the peer endpoint from the config file: de3.vpn.airdns.org
I attached the result as a screenshot.
Here's the relevant part of the log file when I tried to connect with WireGuard using the same config file:

2024-06-26 20:17:27.311208: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Starting WireGuard/0.5.3 (Windows 6.1.7601; amd64)
2024-06-26 20:17:27.311208: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Watching network interfaces
2024-06-26 20:17:27.330808: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Resolving DNS names
2024-06-26 20:17:27.606009: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Creating network adapter
2024-06-26 20:17:27.976211: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Using existing driver 0.10
2024-06-26 20:17:28.344616: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Creating adapter
2024-06-26 20:17:30.293430: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Using WireGuardNT/0.10
2024-06-26 20:17:30.293430: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Enabling firewall rules
2024-06-26 20:17:30.047627: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Interface created
2024-06-26 20:17:30.325630: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Dropping privileges
2024-06-26 20:17:30.326630: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Setting interface configuration
2024-06-26 20:17:30.327630: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Setting device v4 addresses
2024-06-26 20:17:30.326630: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Peer 1 created
2024-06-26 20:17:30.327630: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending keepalive packet to peer 1 (127.106.0.2:1637)
2024-06-26 20:17:30.327630: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:17:30.327630: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Interface up
2024-06-26 20:17:31.142845: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Setting device v6 addresses
2024-06-26 20:17:31.420046: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Startup complete
2024-06-26 20:17:35.492701: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:17:40.689157: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:17:45.869181: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:17:51.030393: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.106.0.2:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-26 20:17:51.030393: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:17:56.286012: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.106.0.2:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-26 20:17:56.286012: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:01.534445: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.106.0.2:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-26 20:18:01.534445: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:06.739078: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:12.023526: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.106.0.2:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-26 20:18:12.023526: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:17.286779: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.106.0.2:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-26 20:18:17.286779: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:22.400609: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:27.400847: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:32.528286: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.106.0.2:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-26 20:18:32.528286: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:37.787327: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.106.0.2:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-26 20:18:37.787327: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:42.874169: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:48.037380: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.106.0.2:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-26 20:18:48.037380: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:53.275209: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.106.0.2:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-26 20:18:53.275209: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:18:58.339424: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:19:03.523655: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Handshake for peer 1 (127.106.0.2:1637) did not complete after 5 seconds, retrying (try 2)
2024-06-26 20:19:03.523655: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Sending handshake initiation to peer 1 (127.106.0.2:1637)
2024-06-26 20:19:05.100124: [MGR] [AirVPN_Germany_UDP-1637-Entry3] Tunnel service tracker finished
2024-06-26 20:19:10.465840: [TUN] [AirVPN_Germany_UDP-1637-Entry3] Shutting down

Please provide me with specific instructions how to troubleshoot this!

Thanks,
Tom
P.S. Is it possible that the config generator uses invalid peer endpoint data? E.g. "Endpoint = de3.vpn.airdns.org:1637" does NOT work, but "Endpoint = 178.162.212.216:1637" created with the option "Resolved hosts" activated DOES work. Maybe you can try it yourself (I attached the two config files again, but maybe you create them yourself)?

AirVPN_Germany_UDP-1637-noDNS.conf AirVPN_Germany_UDP-1637-DNS.conf

Edited ... by Greyzy
added P.S. & 2 files

go558a83nk

Do you get this same result when you're connected to the VPN using the config that works?

Things definitely seem wrong in the test above. Are you running a proxy on your local network? Seems you've got something proxying your traffic so it replies with a local IP in order to tunnel traffic through the proxy to the real final destination. But that won't work for VPNs trying to connect.

ANSWERED Can't connect via WireGuard anymore

Recommended Posts

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Share this post

Link to post

Join the conversation