VPN

944 readers

1 users here now

A community for VPN users and those who want to know more about them.

founded 1 year ago

MODERATORS

dvdnet90@lemmy.world

moeka89@lemm.ee

ardi62@lemmy.wtf

Handshake for peer did not complete: What is blocking my Wireguard connection to Surfshark? (lemmy.world)

submitted 1 year ago by TeeBee@lemmy.world to c/vpn@lemmy.world

2 comments fedilink hide all child comments

I'm using a Surfshark VPN and want to connect to Surfshark via the Wireguard protocol. I have installed the Wireguard program, downloaded the configuration file from the Surfshark website with the keys generated by Surfshark. However, when i press 'Activate' it keeps initiating a handshake but never completes.

Things i have tried:

Opening ports on windows firewall
Googling
Forwarding ports on router
Changing settings in the config file

What am i missing?

top 2 comments

sorted by: hot top controversial new old

[–] seemebreakthis@lemm.ee 1 points 1 year ago (1 children)

Just speculating. Can't test it out for you because I no longer use Surfshark.

Surfshark insists on using MSS Clamping. In your config file, try adding the following line:

PostUp = iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS ---clamp-mss-to-pmtu

I know for a fact that this works for Wireguard running on Linux. But for Windows, I have no clue if the command is the same. If not, try searching for adding MSS Clamping to your Wireguard connection profile.

[–] TeeBee@lemmy.world 1 points 1 year ago

Thanks for the reply!

I tried your suggestion, but it didn't work. Last week I've set up a Linux server that uses a VPN via wireguard and that works fine.