# Self Hosted Forum Log In Issues

**URL:** https://meta.discourse.org/t/self-hosted-forum-log-in-issues/406526
**Category:** Self-hosting
**Tags:** login, cloudflare
**Created:** [July 1, 2026, 10:56am UTC](https://meta.discourse.org/t/self-hosted-forum-log-in-issues/406526 "2026-07-01T10:56:33Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Apiento](https://avatars.discourse-cdn.com/v4/letter/a/c0e974/32.png) [@Apiento](https://meta.discourse.org/u/Apiento)
#### Post date: [July 1, 2026, 10:56am UTC](https://meta.discourse.org/t/self-hosted-forum-log-in-issues/406526/1 "2026-07-01T10:56:34Z")

</div>

Hey All. I have quite a vibrant music loving community called Test Pressing but Discourse has started doing this really weird thing where it is looging us all out. Even as admin I can’t log in to my own forum now… Is this a Cloudflare issue do you think? I am the most un technical person going but just wondering if anyone else has experienced this? I just managed to log in but it literally took me ten goes and a few refreshes all with the same user / pw info. Weird!

> **[Test Pressing - Music People](https://forum.testpressing.org/login)**
>
> A music community from all corners

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [July 1, 2026, 11:04am UTC](https://meta.discourse.org/t/self-hosted-forum-log-in-issues/406526/2 "2026-07-01T11:04:42Z")

</div>

From what I can gather, it looks like an issue with cloudflare’s proxy. Do you have cloudflare’s optimisations turned on? (i.e. the cloud is orange for this host name?) if so, try disabling it and see if situation improves.

Did you follow some guide to configure cloudflare for this site? it is a fairly advanced concept and needs some understanding of discourse and how cloudflare’s optimizations work in order to get it all right.

---

<div class="post-metadata">

### Author: ![itsbhanusharma](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/itsbhanusharma/32/180717_2.png) [@itsbhanusharma](https://meta.discourse.org/u/itsbhanusharma)
#### Post date: [July 1, 2026, 11:06am UTC](https://meta.discourse.org/t/self-hosted-forum-log-in-issues/406526/3 "2026-07-01T11:06:34Z")

</div>

Possibly unrelated but you may want to take a look at

> [@Handling the "chain of trust" of the end user's real IP](https://meta.discourse.org/t/handling-the-chain-of-trust-of-the-end-users-real-ip/406372):
>
> Background Discourse needs to be aware of the end user’s real IP address. However, an end user never directly connects to Discourse since there is always one or more upstream web servers (nginx running in the Discourse container) in place. Thus, we need a way to pass along that information to Discourse in a trusted manner. The x-forwarded-for header is the solution. In this topic I will describe the specific mechanisms for properly handling that information and how we’re expecting it to be pro…

> [@Commit b4a3389 更新后如何获取用户ip](https://meta.discourse.org/t/commit-b4a3389-ip/406267):
>
> 在更新完 所有用户的最后使用地址都变为了docker的网关如 172.17.0.1 我使用的架构如 cloudflare → VPS Nginx → Discourse docker Nginx → Discourse

---

<div class="post-metadata">

### Author: ![Lilly](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/lilly/32/575047_2.png) [@Lilly](https://meta.discourse.org/u/Lilly)
#### Post date: [July 2, 2026, 9:02pm UTC](https://meta.discourse.org/t/self-hosted-forum-log-in-issues/406526/4 "2026-07-02T21:02:21Z")

</div>

yea this is almost certainly a misconfigured cloudflare configuration - did you (or anyone else) make any recent changes in the cloudflare dashboard? like `@itsbhanusharma` said, i would disable the proxy cloud first to see if that fixes it temporarily (may have to wait a few minutes or clear your brower cache).

if cloudflare was recently setup, i would also make sure rocket loader isn’t enabled on cloudflare and SSL/TLS encryption mode is set to `Full (Strict)`. make sure you have the cloudflare template configured properly in your `app.yml` file.
