# Key XXX not initialized (yet), dropping packet

**URL:** <https://forum.pritunl.com/t/key-xxx-not-initialized-yet-dropping-packet/1764>\
**Category:** Pritunl VPN\
**Created:** [January 30, 2024, 3:11pm UTC](https://forum.pritunl.com/t/key-xxx-not-initialized-yet-dropping-packet/1764 "2024-01-30T15:11:12Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![BenjaDiaz](https://forum.pritunl.com/user_avatar/forum.pritunl.com/benjadiaz/32/723_2.png) [@BenjaDiaz](https://forum.pritunl.com/u/BenjaDiaz)\
**Post date:** [January 30, 2024, 3:11pm UTC](https://forum.pritunl.com/t/key-xxx-not-initialized-yet-dropping-packet/1764/1 "2024-01-30T15:11:12Z")

</div>

We are seeing that most times we try to connect to the server we get this error and can’t connect to the network. Sometimes though, this issue does not happen and connectivity is successful.

We are enterprise customers using Mac OS client latest version.

---

<div class="post-metadata">

**Author:** ![zach](https://forum.pritunl.com/user_avatar/forum.pritunl.com/zach/32/1105_2.png) [@zach](https://forum.pritunl.com/u/zach)\
**Post date:** [January 30, 2024, 4:37pm UTC](https://forum.pritunl.com/t/key-xxx-not-initialized-yet-dropping-packet/1764/2 "2024-01-30T16:37:23Z")

</div>

This is typically the issue documented in the [**RHEL connection fix**](https://docs.pritunl.com/docs/rhel-connection-fix) section.

---

<div class="post-metadata">

**Author:** ![BenjaDiaz](https://forum.pritunl.com/user_avatar/forum.pritunl.com/benjadiaz/32/723_2.png) [@BenjaDiaz](https://forum.pritunl.com/u/BenjaDiaz)\
**Post date:** [February 1, 2024, 8:19pm UTC](https://forum.pritunl.com/t/key-xxx-not-initialized-yet-dropping-packet/1764/3 "2024-02-01T20:19:46Z")

</div>

Thanks for the reply, Zach! It effectively was solved applying that fix.

One observation though:

> This issue will only occur on UDP servers, TCP can also be used as a workaround.

This was not the case for us. Even when using TCP servers, we experienced the same issue.