# Wireguard tunnel only works for like 20 minutes. Then it stops **URL:** \ **Category:** General\ **Tags:** security, login-only\ **Created:** [June 17, 2024, 9:23pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391 "2024-06-17T21:23:15Z")\ **Posts on this page:** 11\ **Page:** 1
**Author:** ![armando](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/armando/32/14084_2.png) [@armando](https://community.fly.io/u/armando)\ **Post date:** [June 17, 2024, 9:23pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/1 "2024-06-17T21:23:15Z")
I´ve been using wireguard tunnels for a while. But for some reason a week ago I realized that my tunnels were not working. What I do: `fly wireguard create` Choose my organization, then, type a name to create a file. Import the tunnel and activate it. It works **After like 20 minutes, it stops working and can’t connect again. I checked the logs and it times out waiting for handshake response** **Does anyone has any idea what could it be? Then, if I go and create a new tunnel it works** Thanks in advance. PS: I am using Windows 11 Logs: ```plaintext 2024-06-17 18:17:13.203823: [TUN] [flyio-wireguard] Starting WireGuard/0.5.3 (Windows 10.0.22631; amd64) 2024-06-17 18:17:13.203823: [TUN] [flyio-wireguard] Watching network interfaces 2024-06-17 18:17:13.204853: [TUN] [flyio-wireguard] Resolving DNS names 2024-06-17 18:17:13.452304: [TUN] [flyio-wireguard] Creating network adapter 2024-06-17 18:17:13.490587: [TUN] [flyio-wireguard] Using existing driver 0.10 2024-06-17 18:17:13.494120: [TUN] [flyio-wireguard] Creating adapter 2024-06-17 18:17:13.559903: [TUN] [flyio-wireguard] Using WireGuardNT/0.10 2024-06-17 18:17:13.559903: [TUN] [flyio-wireguard] Enabling firewall rules 2024-06-17 18:17:13.547808: [TUN] [flyio-wireguard] Interface created 2024-06-17 18:17:13.561462: [TUN] [flyio-wireguard] Dropping privileges 2024-06-17 18:17:13.561462: [TUN] [flyio-wireguard] Setting interface configuration 2024-06-17 18:17:13.561976: [TUN] [flyio-wireguard] Peer 1 created 2024-06-17 18:17:13.564041: [TUN] [flyio-wireguard] Sending keepalive packet to peer 1 (redacted-ip-1:51820) 2024-06-17 18:17:13.564041: [TUN] [flyio-wireguard] Sending handshake initiation to peer 1 (redacted-ip-1:51820) 2024-06-17 18:17:13.564041: [TUN] [flyio-wireguard] Interface up 2024-06-17 18:17:13.564041: [TUN] [flyio-wireguard] Monitoring MTU of default v4 routes 2024-06-17 18:17:13.565330: [TUN] [flyio-wireguard] Setting device v4 addresses 2024-06-17 18:17:13.566743: [TUN] [flyio-wireguard] Monitoring MTU of default v6 routes 2024-06-17 18:17:13.567372: [TUN] [flyio-wireguard] Setting device v6 addresses 2024-06-17 18:17:13.568786: [TUN] [flyio-wireguard] Startup complete 2024-06-17 18:17:18.599035: [TUN] [flyio-wireguard] Handshake for peer 1 (redacted-ip-1:51820) did not complete after 5 seconds, retrying (try 2) 2024-06-17 18:17:18.599035: [TUN] [flyio-wireguard] Sending handshake initiation to peer 1 (redacted-ip-1:51820) 2024-06-17 18:17:23.667966: [TUN] [flyio-wireguard] Sending handshake initiation to peer 1 (redacted-ip-1:51820) 2024-06-17 18:17:28.739699: [TUN] [flyio-wireguard] Handshake for peer 1 (redacted-ip-1:51820) did not complete after 5 seconds, retrying (try 2) 2024-06-17 18:17:28.739699: [TUN] [flyio-wireguard] Sending handshake initiation to peer 1 (redacted-ip-1:51820) 2024-06-17 18:17:33.857072: [TUN] [flyio-wireguard] Handshake for peer 1 (redacted-ip-1:51820) did not complete after 5 seconds, retrying (try 2) 2024-06-17 18:17:33.857072: [TUN] [flyio-wireguard] Sending handshake initiation to peer 1 (redacted-ip-1:51820) 2024-06-17 18:17:38.862401: [TUN] [flyio-wireguard] Sending handshake initiation to peer 1 (redacted-ip-1:51820) 2024-06-17 18:17:43.886618: [TUN] [flyio-wireguard] Handshake for peer 1 (redacted-ip-1:51820) did not complete after 5 seconds, retrying (try 2) 2024-06-17 18:17:43.886618: [TUN] [flyio-wireguard] Sending handshake initiation to peer 1 (redacted-ip-1:51820) 2024-06-17 18:17:49.002654: [TUN] [flyio-wireguard] Handshake for peer 1 (redacted-ip-1:51820) did not complete after 5 seconds, retrying (try 2) 2024-06-17 18:17:49.002654: [TUN] [flyio-wireguard] Sending handshake initiation to peer 1 (redacted-ip-1:51820) 2024-06-17 18:17:54.169796: [TUN] [flyio-wireguard] Handshake for peer 1 (104.225.8.204:51820) did not complete after 5 seconds, retrying (try 2) ..... ``` ---
**Author:** ![armando](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/armando/32/14084_2.png) [@armando](https://community.fly.io/u/armando)\ **Post date:** [June 20, 2024, 2:27pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/2 "2024-06-20T14:27:05Z")
Bumping up this thread… Does anyone have any insights? ---
**Author:** ![lubien](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/lubien/32/41919_2.png) [@lubien](https://community.fly.io/u/lubien)\ **Post date:** [June 20, 2024, 2:36pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/3 "2024-06-20T14:36:18Z")
Hey there. Thanks for bumping this. Since I don’t have much context on wg internals I’ve raised this to our Product Security team. ---
**Author:** ![lubien](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/lubien/32/41919_2.png) [@lubien](https://community.fly.io/u/lubien)\ **Post date:** [June 20, 2024, 2:36pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/4 "2024-06-20T14:36:44Z")
Added #security ---
**Author:** ![armando](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/armando/32/14084_2.png) [@armando](https://community.fly.io/u/armando)\ **Post date:** [June 20, 2024, 3:32pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/5 "2024-06-20T15:32:46Z")
@lubien thanks for the response. Hoping to hear back soon! ---
**Author:** ![thomas](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/thomas/32/40188_2.png) [@thomas](https://community.fly.io/u/thomas)\ **Post date:** [June 20, 2024, 5:37pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/6 "2024-06-20T17:37:45Z")
Armando: you have nerd-sniped us. The WireGuard nerds here are all looking at this. Sorry if I missed this, but can you tell us the name of the WireGuard peer that you loaded that died in 20 minutes? Did you create it within the last week, or is this one you created a long time ago? Do you know if you’re using current `flyctl`? We did some minor surgery on how we track peers about a month and a half ago and we want to rule some things out. If you’re seeing this, other people are seeing it too, so thank you for calling this out. ---
**Author:** ![armando](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/armando/32/14084_2.png) [@armando](https://community.fly.io/u/armando)\ **Post date:** [June 20, 2024, 6:55pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/7 "2024-06-20T18:55:55Z")
Well … Now that you mentioned it, I checked `fly version` and it was in fact outdated. Weird, cause I had it set up for auto-update. So I updated to the latest version and I am more than 30 minutes using the tunnel and hasn’t dropped the connection. I notice that new created peers starts with `static-....` the failing ones started with `interactive-...` I am going to use it a little further and provide an update later today. But I am fairly hopeful that updating the CLI solved it. Answering your other question: The older tunnels stopped working as well. Thanks ---
**Author:** ![thomas](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/thomas/32/40188_2.png) [@thomas](https://community.fly.io/u/thomas)\ **Post date:** [June 20, 2024, 8:13pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/8 "2024-06-20T20:13:49Z")
We’ve reproduced this problem. Updating `flyctl` should have fixed it for you (newer `flyctl` generates peers from `flyctl wireguard create` with slightly different metadata that doesn’t trigger garbage collection). If you’re stuck with older `flyctl` somewhere, we can give you an immediate workaround; in the meantime, we’re looking into a global fix on our side. Thanks for calling this out! ---
**Author:** ![armando](https://sea1.discourse-cdn.com/fly1/user_avatar/community.fly.io/armando/32/14084_2.png) [@armando](https://community.fly.io/u/armando)\ **Post date:** [June 21, 2024, 1:23am UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/9 "2024-06-21T01:23:54Z")
Well, thanks for the reply. After a few hours working fine and not closing. I can say, on my case, updating to the newer version of `flyctl` it created the right peers with the right configuration. Marking this as the solution. Thanks for the help ---
**Author:** ![scriptjs](https://avatars.discourse-cdn.com/v4/letter/s/e8c25b/32.png) [@scriptjs](https://community.fly.io/u/scriptjs)\ **Post date:** [June 23, 2024, 2:05pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/10 "2024-06-23T14:05:40Z")
Thanks @armando. Same issue with MacOS. All my old tunnels stopped working and prevented dns on my local system when activated. They worked before I left work for a few weeks ago. Last upgrade on flyctl was 0.2.42 that was released April 24. Mine also were named with “interactive-_" while new begin with "static-_” ---
**Author:** ![system](https://global.discourse-cdn.com/fly1/original/3X/6/e/6e8955d00cb218e186ebbe3a6ab06fefdce15290.svg) [@system](https://community.fly.io/u/system)\ **Post date:** [June 30, 2024, 2:05pm UTC](https://community.fly.io/t/wireguard-tunnel-only-works-for-like-20-minutes-then-it-stops/20391/11 "2024-06-30T14:05:48Z")
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.