Nginx – Get the correct SERVER_ADDR on Apache when using nginx as reverse proxy

apache-2.4nginxreverse-proxy

(see edit below)

I have nginx forwarding requests to Apache 2.4 and I'm getting 127.0.0.1 as the value of SERVER_ADDR. The correct IP is available only on HTTP_X_SERVER_ADDRESS.

I have installed the rpaf module, but it only fixed the REMOTE_ADDR value (which was previously also 127.0.0.1 and now is the correct remote IP).

Is there any way to get the correct server IP on SERVER_ADDR?

I have the following config on nginx.conf:

proxy_set_header X-Real-IP  $remote_addr;
proxy_set_header X-Forwarded-For $remote_addr;
proxy_set_header X-Server-Address $server_addr;
proxy_set_header Host $host;

EDIT: I just realized that I can use proxy_pass [my-server-ip] instead of proxy_pass 127.0.0.1, are there any drawbacks to that?

Best Answer

For nginx-to-apache in same host and single public IP address (for example 192.168.99.1), there are several available options:

Nginx listen on 192.168.99.1 port 80 and and Apache listen on 192.168.99.1 on other ports except 80 (for example port 8080)
Nginx listen on 192.168.99.1 port 80 and and Apache listen on 127.0.0.1 on port 80 (the same port)

The drawback of option 2 was your earlier problem. And for option 1, you shouldn't have any major drawbacks except some firewall rule to ensure that client not direct connecting to Apache port.

Related Solutions

Nginx Configuration – Front-End Reverse Proxy to Another Port

I'm assuming that nginx is not the server listening on port 5010 as well as 80, correct? Something else is listening on 5010 and you wish to have nginx proxy to that server?

If that's the case, here's a nice sample config I've used in the past with success:

server {
        listen       80;
        server_name  <YOUR_HOSTNAME>;
        location / {
            proxy_pass         http://127.0.0.1:5010/;
            proxy_redirect     off;

            proxy_set_header   Host             $host;
            proxy_set_header   X-Real-IP        $remote_addr;
            proxy_set_header   X-Forwarded-For  $proxy_add_x_forwarded_for;

            client_max_body_size       10m;
            client_body_buffer_size    128k;

            proxy_connect_timeout      90;
            proxy_send_timeout         90;
            proxy_read_timeout         90;

            proxy_buffer_size          4k;
            proxy_buffers              4 32k;
            proxy_busy_buffers_size    64k;
            proxy_temp_file_write_size 64k;
        }
}

I believe that should accomplish what you're seeking. Good luck!

NGINX Reverse Proxy – URL Rewrite

Any redirect to localhost doesn't make sense from a remote system (e.g. client's Web browser). So the rewrite flags permanent (301) or redirect (302) are not usable in your case.

Please try following setup using a transparent rewrite rule:

location  /foo {
  rewrite /foo/(.*) /$1  break;
  proxy_pass         http://localhost:3200;
  proxy_redirect     off;
  proxy_set_header   Host $host;
}

Use curl -i to test your rewrites. A very subtle change to the rule can cause nginx to perform a redirect.

Best Answer

Related Solutions

Nginx Configuration – Front-End Reverse Proxy to Another Port

NGINX Reverse Proxy – URL Rewrite

Related Topic