Hello, I’ve deployed Discourse on my own server, everything works normally except detecting user’s IP address, I’ve even made a php script (outside docker container) to get all headers where IP can be: REMOTE_ADDR: 212.58.xxx.xxx SERVER_PORT: 80 SERVER_ADDR: 85.25.xxx.xxx SERVER_SOFTWARE: Apache: HTTP_CF_CONNECTING_IP: 212.58.xxx.xxx HTTP_CDN_LOOP: cloudflare HTTP_X_REAL_IP: 162.158.xxx.xxx Details: Server has BrainyCP panel installed with Apache and Nginx (currently website uses Nginx, which reverse proxies the docker container) HTTP_CF_CONNECTING_IP gives 127.0.0.1 inside docker container, but outside they have normal values Without changing the header using custom commands, Discourse displays server’s IP. (Soon will add more details as my Discourse instance is now rebuilding)

The answer was linked above. You need something like this. [תמונה]Run other websites on the same machine as Discourse and editing the server_name and location stanza like this: server_name discourse.example.com; # <-- change this location / { proxy_pass http://unix:/var/discourse/shared/standalone/nginx.http.sock:; proxy_set_header Host $http_host; proxy_http_version 1.1; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header X-Real-IP $remote_addr; }

I’m not really sure about your setup, but noticed cloudflare in your post. Did you add the CloudFlare template to your app.yml file? - "templates/cloudflare.template.yml" [image] EDIT: used the wrong " "

No, I’ve added it to the templates list, now waiting for rebuild

Rebuilded, but it still shows server IP (I’ve commented custom commands ## Any custom commands to run after building run: - exec: echo "Beginning of custom commands" ## If you want to set the 'From' email address for your first registration, uncomment and change: ## After getting the first signup email, re-comment the line. It only needs to run once. - exec: rails r "SiteSetting.notification_email='noreply@zeronet.space'" #- replace: # filename: /etc/nginx/conf.d/discourse.conf # from: "types {" # to: | # set_real_ip_from 85.25.134.45; # real_ip_header CF-Connection-IP; # real_ip_recursive on; # types { #- replace: # filename: /etc/nginx/conf.d/discourse.conf # from: $proxy_add_x_forwarded_for # to: $send_http_cf_connection_ip; # global: true - exec: echo "End of custom commands" Do I need to uncomment them? (also want to notice that they not worked even before I’ve added cloudflare template to app.yml))

Uncommented, $sent_http_cf_connection_ip gives 127.0.0.1 [image]

Nginx is likely reporting 127.0.0.1 not Discourse it self, you will probably need to set up realip in nginx

I’ve already added cloudflare.template.yml which adds realip directives, but still not working. I’ve even removed custom commands which are changing to custom header and now Discourse reports server IP for all users instead of localhost.

Also this is the Nginx config for domain zeronet.space generated by the panel itself server { listen 85.25.xxx.xx:443 ssl http2; server_name zeronet.space www.zeronet.space; root /home/ay0ks/workspace/sites/zeronet.space; # ssl on; ssl_certificate /etc/certs/ay0ks/zeronet.space_1655753906.crt; ssl_certificate_key /etc/certs/ay0ks/zeronet.space_1655753906.key; #ssl_protocols TLSv1 TLSv1.1 TLSv1.2; #ssl_ciphers "HIGH:!RC4:!aNULL:!MD5:!kEDH"; ssl_protocols TLSv1 TLSv1.1 TLSv1.2 TLSv1.3; ssl_ciphers TLS13-CHACHA20-POLY1305-SHA256:TLS13-AES-128-GCM-SHA256:TLS13-AES-256-GCM-SHA384:ECDHE:!COMPLEMENTOFDEFAULT; ssl_prefer_server_ciphers on; add_header Strict-Transport-Security 'max-age=604800'; access_log /etc/nginx/vhost_logs/zeronet.space_access; error_log /etc/nginx/vhost_logs/zeronet.space_error; location ~ /.well-known { allow all; } location ~ /\.ht { deny all; access_log off; log_not_found off; } location / { root /home/ay0ks/workspace/sites/zeronet.space; proxy_pass http://85.25.xxx.xx:31080; # Discourse is deployed on ports 31080/31443 proxy_redirect off; proxy_force_ranges on; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme; proxy_set_header HTTPS $scheme; proxy_cache off; proxy_cache_key "$request_method|$http_if_modified_since|$http_if_none_match|$host|$request_uri"; #access_log /etc/nginx/vhost_logs//home/ay0ks/workspace/sites/zeronet.space; proxy_cache_valid 3s; proxy_cache_min_uses 2; # proxy_cache_lock on; # proxy_cache_use_stale error timeout; # proxy_cache_use_stale updating http_502 http_504; limit_conn lone 100; # limit_req zone=ltwo burst=10; client_body_buffer_size 128k; client_max_body_size 1024m; proxy_connect_timeout 180; proxy_send_timeout 180; proxy_read_timeout 180; send_timeout 180; proxy_buffer_size 4k; proxy_buffers 8 32k; proxy_busy_buffers_size 68k; proxy_temp_file_write_size 10m; } # error_page 404 /404.html; # error_page 500 502 503 504 /50x.html; } Also I want to note the “path” of request: User -> Cloudflare -> Server(Nginx -> Docker -> Discourse) And note that user’s IP is visible outside docker in cloudflare’s header CF-Connecting-IP

I don’t know a lot about how the Cloudflare real IP stuff works but my suspicion is that your Discourse nginx will need set_real_ip_from to be the IP address that it sees your proxy nginx as. 127.0.0.1? Some other internal address? The public address? Not sure which it would see. Once you know what address that is, I think what I would do is leave the cloudflare template in there, then add a new replace just for set_real_ip_from. In addition to that, your proxy nginx will need to be configured to pass along the CF-Connecting-IP header if it isn’t already configured to do so or doesn’t already do so by default. I can’t really help with this bit.

Same path as me, my issue was nginx wasn’t configured to take the docker IP as a range to set the realip on. set_real_ip_from 172.18.0.0/16; real_ip_header X-Forwarded-For; real_ip_recursive on; set_real_ip_from 172.18.0.0/16; So i go User > Cloudflare > Server Nginx (SWAG Docker) > Discourse proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Host $host; proxy_set_header X-Forwarded-Proto https; proxy_set_header X-Forwarded-Ssl on; proxy_set_header X-Real-IP $remote_addr; templates: - "templates/postgres.template.yml" - "templates/redis.template.yml" - "templates/web.template.yml" - "templates/web.ratelimited.template.yml" ## Uncomment these two lines if you wish to add Lets Encrypt (https) # - "templates/web.ssl.template.yml" # - "templates/web.letsencrypt.ssl.template.yml" # - "templates/web.socketed.template.yml" - "templates/cloudflare.template.yml"

[תמונה] ay0ks: BrainyCP panel installed with Apache and Nginx This could be the cause of your problems. Try setting up discourse on a server without any panels or reverse proxies installed and report if you experience the same problem. As a first step, start by ammending the location block for discourse to match up with the details provided here: Run other websites on the same machine as Discourse

Discourse מציג את כתובת ה-IP של השרת/localhost ככתובת ה-IP של המשתמש

תמיכה התקנה

ay0ks (ay0ks) 12 ביולי,‏ 2022,‏ 2:18pm 19

This fixed issues with ip detection (now everything works normal) but now some of images are not loading

EDIT: this was a cache issue, now everything works! Thank you all!

נושא		תגובות	צפיות
Discourse with jwilder/nginx-proxy howtos? Self-hosting	11	8506	6 באפריל,‏ 2019
All users have the same IP (the Servers IP)? Self-hosting	13	4525	28 ביולי,‏ 2018
Remote users IPV6 address shows as localhost Product Support	30	5510	13 בספטמבר,‏ 2020
Only allow Cloudflare IPs for Discourse server Self-hosting	15	3944	22 בספטמבר,‏ 2017
IP address of users showing as server IP Self-hosting	4	1529	23 בינואר,‏ 2020

Discourse מציג את כתובת ה-IP של השרת/localhost ככתובת ה-IP של המשתמש

נושאים קשורים