Hi, My Discourse is run with reverse proxy (NPM) the discourse don’t it does not support the x-forwarded field and therefore shows me all the time the ip address of my reverse proxy when we look for example from which ip the user is registering etc … I sniff the request on discourse and the X-forw…

See How to set up Discourse on a server with existing Apache sites - sysadmin - Discourse Meta for an example of how to conduits) configure the internal nginx for your reverse proxy ip.

I am struggling with this, too. I have a Debian server with Apache 2.4 vHosts and one of these vHosts is the Discourse Docker container. On Apache the mod_remoteip is enabled (there was no mod_extract_forwarded), but without any configuration options. The vHost config is pretty simple: RequestHead…

Did you add the stuff to see that the remote ip address gets to discourse or do all users appear to be coming from the proxy? Search for x-forwarded-for

Ehm… :see_no_evil: I forgot the Nginx (Discourse) part. :see_no_evil: Thank you! :slight_smile: I just edited app.yml and ran a rebuild on the container. The bot came back almost instantly after the container came back up. I do not see any 429 errors, yet. Hopefully it stays that way for “normal” u…

Problem mit Fehler 429 bei Reverse Proxy

Unterstützung Installation

pfaffman (Jay Pfaffman) 1. Dezember 2020 um 13:58 2

Siehe Set up Discourse on a server with existing Apache sites für ein Beispiel, wie man den internen Nginx für deine Reverse-Proxy-IP konfiguriert.

1 „Gefällt mir“

Thema		Antworten	Aufrufe
Troubleshooting a 429 (rate limit) Self-hosting	20	5908	9. November 2018
429 Too Many Requests - IP logs disabled - discourse can see 127.0.0.1 only Support	2	638	9. März 2022
Last IP shows Reverse Proxy IP address Support	6	2464	8. Oktober 2022
Rate Limiting w/ Reverse Proxy Self-hosting	3	689	16. November 2021
All IPs recorded as 127.0.0.1 Self-hosting	6	2750	16. Juni 2019

Problem mit Fehler 429 bei Reverse Proxy

Verwandte Themen