# Unable to log in to my https forum after recent upgrade?

**URL:** https://meta.discourse.org/t/unable-to-log-in-to-my-https-forum-after-recent-upgrade/51917
**Category:** Support
**Created:** [23 Ottobre 2016, 5:58am UTC](https://meta.discourse.org/t/unable-to-log-in-to-my-https-forum-after-recent-upgrade/51917 "2016-10-23T05:58:31Z")
**Posts on this page:** 6
**Page:** 1

<div class="post-metadata">

### Author: ![ChrisBeach](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisbeach/32/214628_2.png) [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)
#### Post date: [23 Ottobre 2016, 5:58am UTC](https://meta.discourse.org/t/unable-to-log-in-to-my-https-forum-after-recent-upgrade/51917/1 "2016-10-23T05:58:31Z")

</div>

I’ve just found that I’m unable to log in to my forum after upgrading it a few hours ago. I have tried Google, Facebook and password logins. In all cases, after performing login I’m redirected to the forum as a non-signed-in user. Have just tried ./launcher rebuild app, and have disabled (in app.yml) the only plugin that was modified during the upgrade (Topic List Previews) but this didn’t resolve it.

Any suggestions would be much appreciated!

I’m currently on holiday in Malaysia, which complicates things somewhat! (I wonder if this is related - if this were related to an IP range block, would I see these symptoms?)

---

<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: [23 Ottobre 2016, 6:03am UTC](https://meta.discourse.org/t/unable-to-log-in-to-my-https-forum-after-recent-upgrade/51917/2 "2016-10-23T06:03:49Z")

</div>

Is your site HTTPS or HTTP ?

---

<div class="post-metadata">

### Author: ![ChrisBeach](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisbeach/32/214628_2.png) [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)
#### Post date: [23 Ottobre 2016, 6:09am UTC](https://meta.discourse.org/t/unable-to-log-in-to-my-https-forum-after-recent-upgrade/51917/3 "2016-10-23T06:09:30Z")

</div>

It’s HTTPS. I use an nginx front end proxy outside of Docker

---

<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: [23 Ottobre 2016, 6:10am UTC](https://meta.discourse.org/t/unable-to-log-in-to-my-https-forum-after-recent-upgrade/51917/4 "2016-10-23T06:10:37Z")

</div>

> [@ChrisBeach](#):
>
> I use a front end proxy outside of Docker

see:

[https://meta.discourse.org/t/secure-cookie-flag/28058/40?u=sam](https://meta.discourse.org/t/secure-cookie-flag/28058/40)

---

<div class="post-metadata">

### Author: ![ChrisBeach](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/chrisbeach/32/214628_2.png) [@ChrisBeach](https://meta.discourse.org/u/ChrisBeach)
#### Post date: [23 Ottobre 2016, 6:17am UTC](https://meta.discourse.org/t/unable-to-log-in-to-my-https-forum-after-recent-upgrade/51917/5 "2016-10-23T06:17:07Z")

</div>

Thanks so much Sam.

I added the following to my nginx config and this has fixed the problem.

proxy\_set\_header X-Forwarded-Proto https;

Finally able to breathe, and get back to my honeymoon (wife is fuming!)

---

<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: [23 Ottobre 2016, 8:24am UTC](https://meta.discourse.org/t/unable-to-log-in-to-my-https-forum-after-recent-upgrade/51917/6 "2016-10-23T08:24:14Z")

</div>


