

So I removed the second peer Section from the configuration file (in order to do that, simply right click on the item in the Wireguard application, select "Edit selected tunnel", and remove everthing after and including the second "". Since Surfsharks configuration files have two peers included the Killswitch didn't show up. While the Wireguard application has a Killswitch function it only works, and shows, when there is one peer in the configuration file. The vast majority of operating systems are compatible with it, such as Windows, Linux, Android, macOS and also iOS. WireGuard is a relatively new open-source VPN protocol, and it has already been integrated into the Linux kernel for the best possible performance. But I also wanted a working killswitch, in theory the Wireguard application does have a Killswitch function but I couldn't find it on my machine, so I turned to google again, and voilà I found the solution. WireGuard features when used with Surfshark. At this point you should have a working Wireguard installation without the constant need to re-login.

At that point I downloaded the official Wireguard application for my OS from here and imported the configuration files I wanted (to keep it a little bit more organized I didn't import all 175).
#SURFSHARK WIREGUARD DOWNLOAD#
You download the program from the release tab, run it as admin, connect to a Surfshark server with Wireguard and voilà I have 175 configuration files. Using this program was fairly easy, as long as you have a Windows machine.

After some time spent on google I found this project with which you can dump the Wireguard configuration files, together with the private keys from the Surfshark application. Sadly I couldn't find the configuration files for Wireguard (I am aware that they are working on that though, as can be seen here) so I had to find another solution to get those. Since Surfshark offers the OpenVPN configuration files for their servers, I could have just used those with another OpenVPN Application, but I really didn't want to miss out on the awesome speeds Wireguard delivers. Since I also had to deal with those problems I decided to look for a solution. In the last couple of weeks a lot of people on this subreddit complained about the broken killswitch Surfshark implemented a while ago or that they are constantly need to login again.
