# Sporadic issue wp-discourse/SSO: Nonce has already expired

**URL:** <https://meta.discourse.org/t/sporadic-issue-wp-discourse-sso-nonce-has-already-expired/94353>\
**Category:** WordPress\
**Created:** [9 augustus 2018 om 21:13 UTC](https://meta.discourse.org/t/sporadic-issue-wp-discourse-sso-nonce-has-already-expired/94353 "2018-08-09T21:13:30Z")\
**Posts on this page:** 1\
**Showing post:** 24

<div class="post-metadata">

**Author:** ![ohm-s](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/ohm-s/32/215705_2.png) [@ohm-s](https://meta.discourse.org/u/ohm-s)\
**Post date:** [14 oktober 2021 om 04:32 UTC](https://meta.discourse.org/t/sporadic-issue-wp-discourse-sso-nonce-has-already-expired/94353/24 "2021-10-14T04:32:11Z")

</div>

I faced the same issue after taking a backup of the running Ec2 Instance and launching it again

The nonce relies on having the value set in redis and in session for csrf validation

I turned off the SiteSetting.discourse\_connect\_csrf\_protection which made the login work consistently, but I haven’t debugged why the session is not being set properly yet

---

_[View the full topic](https://meta.discourse.org/t/sporadic-issue-wp-discourse-sso-nonce-has-already-expired/94353)._
