# Gelegentliches Problem wp-discourse/SSO: Nonce ist bereits abgelaufen

**URL:** <https://meta.discourse.org/t/sporadic-issue-wp-discourse-sso-nonce-has-already-expired/94353>\
**Category:** WordPress\
**Created:** [9. August 2018 um 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:** 1

<div class="post-metadata">

**Author:** ![lkramer](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lkramer/32/83897_2.png) [@lkramer](https://meta.discourse.org/u/lkramer)\
**Post date:** [9. August 2018 um 21:13 UTC](https://meta.discourse.org/t/sporadic-issue-wp-discourse-sso-nonce-has-already-expired/94353/1 "2018-08-09T21:13:30Z")

</div>

Hi. We have this sporadic issue a couple of times per month where:

1. a user signs up in WordPress
2. they go to our Discourse forum and press the blue Login button
3. the page hangs for several seconds (about 30) and then we get a 502 bad gateway error and the person is not logged in to Discourse nor is an account created

The URL that’s hanging on is:  
[https://OUR-FORUM-URL/session/sso\_login?sso=LOTS-OF-BIG-LONG-ARGUMENTS](https://OUR-FORUM-URL/session/sso_login?sso=LOTS-OF-BIG-LONG-ARGUMENTS)

Over in the Discourse logs I see this (I’m not including real user info):

`Verbose SSO log: Nonce has already expired nonce: bff3e6d112bb037832af3d0753cc1b3a name: FIRST LAST username: SOME-USERNAME email: SOME-EMAIL-ADDRESS avatar_url: https://secure.gra.....`

I’ve searched here for “Nonce has already expired” but couldn’t find a solution that seemed applicable here. Especially since it’s very sporadically occurring with no clear pattern to it.

Any ideas?

Thanks!

---

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