# 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:** 1
**Showing post:** 3

<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

---

_[View the full topic](https://meta.discourse.org/t/self-hosted-forum-log-in-issues/406526)._