# How to investigate upstream timed out issues?

**URL:** <https://www.ruby-forum.com/t/how-to-investigate-upstream-timed-out-issues/227426>\
**Category:** NGINX\
**Created:** [March 15, 2013, 4:38am UTC](https://www.ruby-forum.com/t/how-to-investigate-upstream-timed-out-issues/227426 "2013-03-15T04:38:15Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![michael.heuberger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/82dd89/32.png) [@michael.heuberger](https://www.ruby-forum.com/u/michael.heuberger)\
**Post date:** [March 15, 2013, 4:38am UTC](https://www.ruby-forum.com/t/how-to-investigate-upstream-timed-out-issues/227426/1 "2013-03-15T04:38:15Z")

</div>

Hello guys

In my nginx version 1.3.14 I’m having lots of upstream timeouts like  
these  
and wonder what’s the correct, professional approach is, to solve these:

example:

762#0: \*113 upstream timed out (110: Connection timed out) while reading  
response header from upstream, client: 58.28.152.233, server:  
[videomail.io](http://videomail.io),  
request: “GET /socket.io/socket.io.v0.9.11.js HTTP/1.1”, upstream:  
“[https://127.0.0.1:4443/socket.io/socket.io.v0.9.11.js](https://127.0.0.1:4443/socket.io/socket.io.v0.9.11.js)”, host:  
“[videomail.io](http://videomail.io)”

relevant nginx config:

location / {  
proxy\_cache one;  
try\_files $uri @proxy;  
}

location @proxy {  
proxy\_set\_header X-Forwarded-For $proxy\_add\_x\_forwarded\_for;  
proxy\_set\_header X-NginX-Proxy true;  
proxy\_set\_header Host $http\_host;

```
proxy_next_upstream error timeout invalid_header http_500 http_502

```

http\_503 http\_504 http\_404;

```
proxy_pass https://127.0.0.1:4443;

proxy_set_header Upgrade $http_upgrade;
proxy_set_header Connection "upgrade";
proxy_http_version 1.1;

```

}

what would you do in my case to examine this? imo the default timeout of  
60  
seconds is good and i do not want to increase it. it should be able to  
deliver socket.io.v0.9.11.js under 60 seconds, so i believe the problem  
is  
something else. i just do not know how to investigate this.

any hints very welcome!

cheers  
michael

Posted at Nginx Forum:

> **[How to investigate upstream timed out issues?](https://forum.nginx.org/read.php?2,237385,237385#msg-237385)**
>
> Hello guys In my nginx version 1.3.14 I'm having lots of upstream timeouts like these and wonder what's the correct, professional approach is, to solve these: example: 762#0: \*113 upstream timed out (110: Connection timed out) while reading response...

---

<div class="post-metadata">

**Author:** ![michael.heuberger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/82dd89/32.png) [@michael.heuberger](https://www.ruby-forum.com/u/michael.heuberger)\
**Post date:** [March 15, 2013, 9:16am UTC](https://www.ruby-forum.com/t/how-to-investigate-upstream-timed-out-issues/227426/2 "2013-03-15T09:16:55Z")

</div>

are you able to fetch the given ressource from your nginx-server?

e.g. wget [https://127.0.0.1:4443/socket.io/socket.io.v0.9.11.js](https://127.0.0.1:4443/socket.io/socket.io.v0.9.11.js)

maybe you have an port-issue (4443 vs 443)

mex

Posted at Nginx Forum:

> **[Re: How to investigate upstream timed out issues?](https://forum.nginx.org/read.php?2,237385,237390#msg-237390)**
>
> Hello guys In my nginx version 1.3.14 I'm having lots of upstream timeouts like these and wonder what's the correct, professional approach is, to solve these: example: 762#0: \*113 upstream timed out (110: Connection timed out) while reading response...

---

<div class="post-metadata">

**Author:** ![michael.heuberger](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/m/82dd89/32.png) [@michael.heuberger](https://www.ruby-forum.com/u/michael.heuberger)\
**Post date:** [March 29, 2013, 2:36am UTC](https://www.ruby-forum.com/t/how-to-investigate-upstream-timed-out-issues/227426/3 "2013-03-29T02:36:48Z")

</div>

No it works with port 4443 (I have opened it somewhere else) but am  
getting  
another wget error message:

> wget [https://videomail.io:4443/socket.io/socket.io.v0.9.11.js](https://videomail.io:4443/socket.io/socket.io.v0.9.11.js)  
> –2013-03-29 14:35:00–  
> [https://videomail.io:4443/socket.io/socket.io.v0.9.11.js](https://videomail.io:4443/socket.io/socket.io.v0.9.11.js)  
> Resolving [videomail.io](http://videomail.io) ([videomail.io](http://videomail.io))… 103.6.212.124  
> Connecting to [videomail.io](http://videomail.io) ([videomail.io](http://videomail.io))|103.6.212.124|:4443…  
> connected.  
> ERROR: cannot verify [videomail.io](http://videomail.io)’s certificate, issued by  
> `/C=US/O=GeoTrust, Inc./CN=RapidSSL CA': Unable to locally verify the issuer's authority. To connect to videomail.io insecurely, use `–no-check-certificate’.

It’s related to the certificate. No idea what’s wrong? How can I examine  
this deeper?

Cheers  
Michael

Posted at Nginx Forum:  
[http://forum.nginx.org/read.php?2,237385,237924#msg-237924](http://forum.nginx.org/read.php?2,237385,237924#msg-237924)