Not connected, Your IP: 3.138.170.67
Online: 25439 users - 294829 Mbit/s total BWLeaderboard
Popular Content
Showing content with the highest reputation on 06/24/24 in all areas
-
1 point
ANSWERED Can't connect via WireGuard anymore
Greyzy reacted to go558a83nk for a post in a topic
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. -
1 point
ANSWERED Can't connect via WireGuard anymore
Greyzy reacted to go558a83nk for a post in a topic
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? -
1 pointThat 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.