# SSO suddenly broken with "Error updating information, contact site admin"

**URL:** https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185
**Category:** Support
**Created:** [April 4, 2015, 6:28am UTC](https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185 "2015-04-04T06:28:40Z")
**Posts on this page:** 9
**Page:** 1

<div class="post-metadata">

### Author: ![swisspol](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/swisspol/32/115586_2.png) [@swisspol](https://meta.discourse.org/u/swisspol)
#### Post date: [April 4, 2015, 6:28am UTC](https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185/1 "2015-04-04T06:28:41Z")

</div>

Running `v1.3.0.beta4 +18`

I just realized my SSO is broken, but I don’t know when it broke (possibly when updating from beta3 to beta4?). Nothing has changed AFAIK on the SSO side.

When I click on Log In it redirects to the SSO site correctly, sign-in works there, but the final redirect to Discourse fails: I get a blank page that just says “Error updating information, contact site admin” (the response headers indicate a 500 error). The logs in the admin interface are completely empty.

How do I debug and fix this?

---

<div class="post-metadata">

### Author: ![codinghorror](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/codinghorror/32/110067_2.png) [@codinghorror](https://meta.discourse.org/u/codinghorror)
#### Post date: [April 4, 2015, 6:29am UTC](https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185/2 "2015-04-04T06:29:53Z")

</div>

Anything in [discourse.example.com/logs](http://discourse.example.com/logs) there?

So you were on beta3 and everything was OK?

---

<div class="post-metadata">

### Author: ![swisspol](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/swisspol/32/115586_2.png) [@swisspol](https://meta.discourse.org/u/swisspol)
#### Post date: [April 4, 2015, 6:50am UTC](https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185/3 "2015-04-04T06:50:40Z")

</div>

No, error logs are empty.

I can’t confirm it’s beta3 to beta4 as the community site hasn’t been launched yet, so almost no one is using it. It was working a few days back as there was one new user who signed in though.

---

<div class="post-metadata">

### Author: ![swisspol](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/swisspol/32/115586_2.png) [@swisspol](https://meta.discourse.org/u/swisspol)
#### Post date: [April 4, 2015, 6:53am UTC](https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185/4 "2015-04-04T06:53:53Z")

</div>

After more investigation, the issue seems to be related to CloudFlare which I have enabled for the domain that hosts discourse. I paused CloudFlare and the issue seemed to have gone away.

---

<div class="post-metadata">

### Author: ![swisspol](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/swisspol/32/115586_2.png) [@swisspol](https://meta.discourse.org/u/swisspol)
#### Post date: [April 4, 2015, 6:54am UTC](https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185/5 "2015-04-04T06:54:24Z")

</div>

Note that I had CloudFlare enabled for the past 2 or 3 months without any SSO issue.

---

<div class="post-metadata">

### Author: ![swisspol](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/swisspol/32/115586_2.png) [@swisspol](https://meta.discourse.org/u/swisspol)
#### Post date: [April 4, 2015, 6:59am UTC](https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185/6 "2015-04-04T06:59:20Z")

</div>

Another thing: even if CloudFlare is enabled, SSO works if I reload the redirect URL after replacing the hostname `forums.gitup.co` by the raw server IP `54.68.80.84` in it e.g.

```
https://forums.gitup.co/session/sso_login?sso=...

```

by

```
http://54.68.80.84/session/sso_login?sso=...

```

---

<div class="post-metadata">

### Author: ![swisspol](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/swisspol/32/115586_2.png) [@swisspol](https://meta.discourse.org/u/swisspol)
#### Post date: [April 4, 2015, 6:59am UTC](https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185/7 "2015-04-04T06:59:54Z")

</div>

How do I look for error logs once SSH’ed into the Docker instance?

---

<div class="post-metadata">

### Author: ![swisspol](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/swisspol/32/115586_2.png) [@swisspol](https://meta.discourse.org/u/swisspol)
#### Post date: [April 5, 2015, 11:06pm UTC](https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185/8 "2015-04-05T23:06:19Z")

</div>

I think I fixed the issue: I noticed randomly this morning that Discourse had automatically added to the list of blocked IP addresses one of the CloudFlare IP addresses. I removed this block then explicitly whitelisted [all their IPs](https://www.cloudflare.com/ips). Then I reenabled CloudFlare, waited a few hours, and login with SSO appears to work again 😄

---

<div class="post-metadata">

### Author: ![sam](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/sam/32/102149_2.png) [@sam](https://meta.discourse.org/u/sam)
#### Post date: [April 6, 2015, 10:19am UTC](https://meta.discourse.org/t/sso-suddenly-broken-with-error-updating-information-contact-site-admin/27185/9 "2015-04-06T10:19:24Z")

</div>


