Do you know if anyone else on the site is running into the same issue?
If the site admins haven’t done it already, they could enable the verbose_discourse_connect_logging. Some details about debugging DiscourseConnect issues with that setting are here: Debug and fixing common DiscourseConnect issues. I’m not sure that topic covers the issue you are running into though.
The full error message that’s shown in the logs for this will be something like: Nonce is incorrect, was generated in a different browser session, or has expired. Possible causes of this are:
- the nonce that’s passed from the application to Discourse on your login attempt doesn’t match the nonce that was initially sent from Discourse to the application
- the nonce was generated in a different session than the session you are logging in from. This will happen if the application is making a background request to get the nonce from Discourse, instead of having it be generated by a browser redirect.
- the user waits longer than 10 minutes (the nonce expiry time) to complete the login
I’m guessing that you’re running into the first issue in that list.