# JWT token invalid after server restart

**URL:** <https://forum.heroiclabs.com/t/jwt-token-invalid-after-server-restart/2113>\
**Category:** Runtime Framework\
**Tags:** authentication\
**Created:** [November 20, 2021, 10:24am UTC](https://forum.heroiclabs.com/t/jwt-token-invalid-after-server-restart/2113 "2021-11-20T10:24:00Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kafka](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/kafka/32/475_2.png) [@kafka](https://forum.heroiclabs.com/u/kafka)\
**Post date:** [November 20, 2021, 10:24am UTC](https://forum.heroiclabs.com/t/jwt-token-invalid-after-server-restart/2113/1 "2021-11-20T10:24:00Z")

</div>

Hi  
When Nakama server restart, clients can not use current JWT token because it is invalid.  
How can client still authenticated without re-authenticate ?

---

<div class="post-metadata">

**Author:** ![Mawiel](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/mawiel/32/477_2.png) [@Mawiel](https://forum.heroiclabs.com/u/Mawiel)\
**Post date:** [November 22, 2021, 1:50pm UTC](https://forum.heroiclabs.com/t/jwt-token-invalid-after-server-restart/2113/2 "2021-11-22T13:50:12Z")

</div>

I am having the same issue. I thought sessions were stored on the server and persist through restart. I am on Nakama server 3.9.0, also tried 3.2.1.

---

<div class="post-metadata">

**Author:** ![tunglt1810](https://sea2.discourse-cdn.com/flex020/user_avatar/forum.heroiclabs.com/tunglt1810/32/924_2.png) [@tunglt1810](https://forum.heroiclabs.com/u/tunglt1810)\
**Post date:** [April 21, 2022, 4:41am UTC](https://forum.heroiclabs.com/t/jwt-token-invalid-after-server-restart/2113/3 "2022-04-21T04:41:52Z")

</div>

Hi guys,

Are you still facing this issue or have a solution?