Forum: NGINX How to investigate upstream timed out issues?

Posted by michael.heuberger (Guest)
on 2013-03-15 04:38
(Received via mailing list)
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,
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", host:
"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: 
http://forum.nginx.org/read.php?2,237385,237385#msg-237385
Posted by mex (Guest)
on 2013-03-15 09:16
(Received via mailing list)
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


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




mex

Posted at Nginx Forum: 
http://forum.nginx.org/read.php?2,237385,237390#msg-237390
Posted by michael.heuberger (Guest)
on 2013-03-29 02:36
(Received via mailing list)
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
--2013-03-29 14:35:00--
https://videomail.io:4443/socket.io/socket.io.v0.9.11.js
Resolving videomail.io (videomail.io)... 103.6.212.124
Connecting to videomail.io (videomail.io)|103.6.212.124|:4443... 
connected.
ERROR: cannot verify 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
Please log in before posting. Registration is free and takes only a minute.
Existing account (Switch to SSL-encrypted connection)
NEW: Do you have a Google/GoogleMail or Yahoo account? No registration required!
Log in with Google account | Log in with Yahoo account
No account? Register here.