Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have stunnel in front of nginx in order to handle ssl. (I'm aware that nginx can handle ssl, but I'm migrating off nginx and this is a necessary step.)

Stunnel and nginx are running on the same box.

Without stunnel in front of nginx, nginx got the server_addr and server_name as the public ip of the box and the domain of the url I was fetching, respectively.

Now with stunnel, nginx thinks the server_addr and server_name are and localhost respectively. This is screwing up a bunch of things.

How can I make nginx get (or stunnel send) the correct server_addr and server_name?

share|improve this question

However, since Stunnel is a proxy an has no knowledge of HTTP, the client's IP address was lost, which is somewhat annoying.

Try ngx_http_realip_module and X-Forwarded-For support for Stunnel:

real_ip_header     X-Forwarded-For;
share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.