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…

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 Error 429 with Reverse proxy

Support Self-hosting

pfaffman (Jay Pfaffman) December 1, 2020, 1:58pm 2

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

Topic		Replies	Views
Troubleshooting a 429 (rate limit) Self-hosting	19	5966	October 10, 2018
429 Too Many Requests - IP logs disabled - discourse can see 127.0.0.1 only Support	1	644	March 9, 2022
Last IP shows Reverse Proxy IP address Support	5	2493	May 22, 2019
Rate Limiting w/ Reverse Proxy Self-hosting	3	719	November 16, 2021
All IPs recorded as 127.0.0.1 Self-hosting	4	2781	June 8, 2017

Problem Error 429 with Reverse proxy

Related topics