Ok so it seams my mistake, everything is fine with this configuration, I need extra step in backend to complete my task, as for specific example I needed to set option in backend server (litespeed web server) option "Use Client IP in Header" I must be accidentally disabled it.by romkaltu - Nginx Mailing List - English
So I have Nginx proxy and some servers running behind it. I need to know real users IP not proxy, so I using real_ip module. Everything is working as expected, but if I configure vhost like subdomain.domain.com backend getting Nginx proxy IP. Here is my Nginx config sample set_real_ip_from 192.168.2.0/24; real_ip_header X-Forwarded-For; real_ip_recursive on; upstream srv1 { server 1by romkaltu - Nginx Mailing List - English
Also: no need to secure front-end to back-end proxy_pass to backend with port :80by romkaltu - Nginx Mailing List - English
Yep this is it, just wanted to update status as somebody from serverfault already told me that :)by romkaltu - Nginx Mailing List - English
What is your backend server? Maybe problem can persist in backend? I'm using Litespeed web server.by romkaltu - Nginx Mailing List - English
Having odd situation, even don't know how to search in google, how to describe it...Anyway I'm using Nginx and proxy'ing https traffic to upstream server. Everything is fine with http (with others domains) but can't get it to work with https... Here is my nginx config upstream umarket { server 192.168.2.11:443; } # Upstream server { listen 80; listen 443 ssl http2; server_by romkaltu - Nginx Mailing List - English