# WireGuard not reachable all of a sudden?

**URL:** <https://dietpi.com/forum/t/wireguard-not-reachable-all-of-a-sudden/17381>\
**Category:** General Discussion\
**Created:** [20 July 2023 19:33 UTC](https://dietpi.com/forum/t/wireguard-not-reachable-all-of-a-sudden/17381 "2023-07-20T19:33:49Z")\
**Posts on this page:** 2\
**Page:** 2

<div class="post-metadata">

**Author:** ![Jappe](https://dietpi.com/forum/user_avatar/dietpi.com/jappe/32/1788_2.png) [@Jappe](https://dietpi.com/forum/u/Jappe)\
**Post date:** [23 July 2023 11:36 UTC](https://dietpi.com/forum/t/wireguard-not-reachable-all-of-a-sudden/17381/21 "2023-07-23T11:36:51Z")

</div>

I think this “DequeueBuffer time out” is something else.  
So no handshake happened, so my guess is the address for the endpoint is wrong or the endpoint is not reachable for some reason.  
For the sake of completness:

- The wireguard port is forwarded?
- Is the format for the endpoint address correct? (`domain:port` or `public_IP:port`)
- If you use a DDNS: Did your IP change recently and the DDNS still has the old one?

For testing you could change the endpoint adress to the local IP and test from within your LAN if you can connect. (to rule out problems with the wireguard config)

---

<div class="post-metadata">

**Author:** ![Joulinar](https://dietpi.com/forum/user_avatar/dietpi.com/joulinar/32/57_2.png) [@Joulinar](https://dietpi.com/forum/u/Joulinar)\
**Post date:** [23 July 2023 17:29 UTC](https://dietpi.com/forum/t/wireguard-not-reachable-all-of-a-sudden/17381/22 "2023-07-23T17:29:36Z")

</div>

As well you could use your external IP address instead of DDNS name inside your client app configuration to exclude issues on that level. One more thing would be to remove and recreate port forwarding within your F!B

[Previous page](https://dietpi.com/forum/t/wireguard-not-reachable-all-of-a-sudden/17381.md?page=1)