# Reverse Proxy - Issue in 0.8.36/.37

**URL:** <https://www.ruby-forum.com/t/reverse-proxy-issue-in-0-8-36-37/189682>\
**Category:** NGINX\
**Created:** [June 5, 2010, 2:05am UTC](https://www.ruby-forum.com/t/reverse-proxy-issue-in-0-8-36-37/189682 "2010-06-05T02:05:01Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![kevin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/2acd7d/32.png) [@kevin](https://www.ruby-forum.com/u/kevin)\
**Post date:** [June 5, 2010, 2:05am UTC](https://www.ruby-forum.com/t/reverse-proxy-issue-in-0-8-36-37/189682/1 "2010-06-05T02:05:01Z")

</div>

I can’t really post my config with all information but I can post the  
specific configuration for the site’s that have issues.

nginx 0.7.x does not show this problem.

If you configure a SSL reverse proxy:  
server {  
listen 192.168.12.2:1001;  
ssl on;  
ssl\_certificate /usr/local/nginx/cert/apache-cert;  
ssl\_certificate\_key /usr/local/nginx/cert/apache-key;  
ssl\_session\_timeout 5m;  
keepalive\_timeout 15;  
location / {  
#limit\_req zone=one burst=10;  
proxy\_read\_timeout 300;  
proxy\_connect\_timeout 300;  
proxy\_pass [http://example.site.com:6043](http://example.site.com:6043);  
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;  
proxy\_set\_header X-Forwarded-Proto https;  
}  
}

Then it always gives ‘Bad Gateway’. This issue was never present with  
0.7.x

Setting proxy\_pass to : https:// or http:// gives the same result.

Enabling or disabling buffering offers the same result.

Any ideas if this is a new bug? I have thus far, tested .36/.37 - I’m  
building .38 now to see if it’s still an issue.

Any help would be greatly appreciated.

Posted at Nginx Forum:

> **[Reverse Proxy - Issue in 0.8.36/.37](https://forum.nginx.org/read.php?2,94684,94684#msg-94684)**
>
> I can't really post my config with all information but I can post the specific configuration for the site's that have issues. nginx 0.7.x does not show this problem. If you configure a SSL reverse proxy: server { listen 192.168.12.2:

---

<div class="post-metadata">

**Author:** ![kevin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/2acd7d/32.png) [@kevin](https://www.ruby-forum.com/u/kevin)\
**Post date:** [June 5, 2010, 2:08am UTC](https://www.ruby-forum.com/t/reverse-proxy-issue-in-0-8-36-37/189682/2 "2010-06-05T02:08:31Z")

</div>

Realized I couldn’t edit my post.

No issues are seen with reverse proxies (that we can tell) when using  
standard ports. It appears to be only on non-standard ports. Firewall  
had been disabled for testing as well.

tcpdump shows the connections going out and a response coming back but  
it immediately drops to a ‘Bad Gateway’. Downgraded to 0.7.xx (newest)  
and the issue was immediately resolved. (Exact same config file, simply  
a restart of the service and it started working again with 0.7)

This issue occurred on two different systems, two different datacenters.

FreeBSD 8.0 x64 / with kqueue

Posted at Nginx Forum:

> **[Re: Reverse Proxy - Issue in 0.8.36/.37](https://forum.nginx.org/read.php?2,94684,94685#msg-94685)**
>
> I can't really post my config with all information but I can post the specific configuration for the site's that have issues. nginx 0.7.x does not show this problem. If you configure a SSL reverse proxy: server { listen 192.168.12.2:

---

<div class="post-metadata">

**Author:** ![kevin](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/k/2acd7d/32.png) [@kevin](https://www.ruby-forum.com/u/kevin)\
**Post date:** [June 5, 2010, 2:18am UTC](https://www.ruby-forum.com/t/reverse-proxy-issue-in-0-8-36-37/189682/3 "2010-06-05T02:18:29Z")

</div>

Hmm…

Actually it appears when I test with 0.8.38:  
If I set:  
gzip on;  
and changed:  
https://  
to http:// and restarted… The issue fixed itself.

Hmmm… Anyway, just a mention. Maybe it was a config issue?

Posted at Nginx Forum:

> **[Re: Reverse Proxy - Issue in 0.8.36/.37](https://forum.nginx.org/read.php?2,94684,94689#msg-94689)**
>
> I can't really post my config with all information but I can post the specific configuration for the site's that have issues. nginx 0.7.x does not show this problem. If you configure a SSL reverse proxy: server { listen 192.168.12.2: