# 4.x Wireguard REKEY-TIMEOUT troubleshooting **URL:** \ **Category:** Router\ **Tags:** Featured\ **Created:** [December 14, 2022, 9:46am UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814 "2022-12-14T09:46:14Z")\ **Posts on this page:** 11\ **Page:** 2
**Author:** ![thekey93](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/t/57b2e6/32.png) [@thekey93](https://forum.gl-inet.com/u/thekey93)\ **Post date:** [March 9, 2023, 9:02pm UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/22 "2023-03-09T21:02:16Z")
Sent you direct message with information ---
**Author:** ![hansome](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/b5ac83/32.png) [@hansome](https://forum.gl-inet.com/u/hansome)\ **Post date:** [March 24, 2023, 6:36am UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/23 "2023-03-24T06:36:42Z")
After testing and researching for so long, I think I have reproduced your same issue. The conclusion is that when the 51820 port is blocked, there will be a situation where the wireguard cannot be connected, and the interface shows that the connection is successful but actually unsuccessful. The [snapshot](https://dl.gl-inet.com/?model=axt1800&type=snapshot) firmware addresses this issue by using a different port to communicate with port 51820 each time it reconnects. If you already add the wireguard conf, and there was a previous auto-generated listen port, please remove it. ![image](https://forum-static.gl-inet.com/original/2X/d/d20d66a888c0c343c8125b9ace20d8588272b61d.png) ---
**Author:** ![SmurfonToast](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/s/65b543/32.png) [@SmurfonToast](https://forum.gl-inet.com/u/SmurfonToast)\ **Post date:** [March 24, 2023, 7:08am UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/24 "2023-03-24T07:08:55Z")
> [@hansome](#): > > The [snapshot](https://dl.gl-inet.com/?model=axt1800&type=snapshot) firmware addresses this issue by using a different port to communicate with port 51820 each time it reconnects. Sounds good. Will this solution be cascaded to all Routers on 4.x F/W e.g. the Beryl AX? ---
**Author:** ![hansome](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/b5ac83/32.png) [@hansome](https://forum.gl-inet.com/u/hansome)\ **Post date:** [March 24, 2023, 7:56am UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/25 "2023-03-24T07:56:20Z")
Yes, it will be applied to all 4.x FW ---
**Author:** ![thekey93](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/t/57b2e6/32.png) [@thekey93](https://forum.gl-inet.com/u/thekey93)\ **Post date:** [March 24, 2023, 1:25pm UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/26 "2023-03-24T13:25:47Z")
@hansome Thank you for the investigation. I will try this snapshot and let you know how it goes. ---
**Author:** ![thekey93](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/t/57b2e6/32.png) [@thekey93](https://forum.gl-inet.com/u/thekey93)\ **Post date:** [March 27, 2023, 3:55pm UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/27 "2023-03-27T15:55:27Z")
@hansome Issue is still present and encountered two days in a row ☹ ---
**Author:** ![hansome](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/b5ac83/32.png) [@hansome](https://forum.gl-inet.com/u/hansome)\ **Post date:** [March 28, 2023, 1:27am UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/28 "2023-03-28T01:27:29Z")
Please generate a configuration backup([http://192.168.8.1/cgi-bin/luci/admin/system/flash](http://192.168.8.1/cgi-bin/luci/admin/system/flash)) and export log([http://192.168.8.1/#/logview](http://192.168.8.1/#/logview)) , send me by PM or email to [handongming@gl-inet.com](mailto:handongming@gl-inet.com) Did the fake wireguard connection happen? or only a system crash? ---
**Author:** ![thekey93](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/t/57b2e6/32.png) [@thekey93](https://forum.gl-inet.com/u/thekey93)\ **Post date:** [March 28, 2023, 2:04pm UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/29 "2023-03-28T14:04:43Z")
@hansome Sent you the files through PM. Looks like system crash and fake wireguard connection happened. I saw exactly same symptoms as before I moved to the snapshot firmware you created. ---
**Author:** ![hansome](https://forum-assets.gl-inet.com/letter_avatar_proxy/v4/letter/h/b5ac83/32.png) [@hansome](https://forum.gl-inet.com/u/hansome)\ **Post date:** [March 28, 2023, 2:17pm UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/30 "2023-03-28T14:17:57Z")
Thank you very much. I’ll check the logs, do some tests, and get back to you asap. ---
**Author:** ![admon](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/admon/32/32880_2.png) [@admon](https://forum.gl-inet.com/u/admon)\ **Post date:** [May 25, 2024, 11:11am UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/31 "2024-05-25T11:11:45Z")
8 posts were split to a new topic: [WireGuard does not work on Opal](https://forum.gl-inet.com/t/wireguard-does-not-work-on-opal/42712) ---
**Author:** ![admon](https://forum-assets.gl-inet.com/user_avatar/forum.gl-inet.com/admon/32/32880_2.png) [@admon](https://forum.gl-inet.com/u/admon)\ **Post date:** [May 25, 2024, 11:44am UTC](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814/32 "2024-05-25T11:44:34Z")
[Previous page](https://forum.gl-inet.com/t/4-x-wireguard-rekey-timeout-troubleshooting/25814.md?page=1)