Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Nginx Proxy timeout

See original GitHub issue

You want to:

report a bug
request a feature

Current behaviour

Nginx randomly logs the following error: upstream timed out (110: Connection timed out) while reading response header from upstream, client: xxxxxx, server: xxxxxxxxx, request: "GET /realtime/?EIO=3&transport=polling&t=xxxxxxxx&sid=xxxxxxxx HTTP/1.1", upstream: "http://127.0.0.1:3000/realtime/?EIO=3&transport=polling&t=xxxxxxxx&sid=xxxxxxxx""

I’m using the same configuration for nginx as on https://github.com/socketio/socket.io/blob/master/examples/cluster-nginx/nginx/nginx.conf.

Steps to reproduce

Start a socket.io server behind a nginx proxy, connect with a client and wait.

Expected behaviour

No errors in nginx error log.

Setup

OS: All of them
browser: All of them
socket.io version: 2.0.1

Issue Analytics

State:
Created 6 years ago
Reactions:5
Comments:9 (2 by maintainers)

Top GitHub Comments

1reaction

Buffelecommented, Mar 14, 2020

Hello all,

Sorry for not replying to this for a long time. I’m still experiencing this issue with the latest socket.io version. Also I’m experiencing the exact same issue like @Steveb-p described. Some users randomly can’t connect to my socket.io instance at all. With literally no error in my logs. I asked them to try another browser and then it worked for them again. This happened so far to Edge and Chrome users. So it’s not specific to a browser. But switching the browser helps “fixing” the issue. However, I never encountered this issue myself.

0reactions

darrachequesnecommented, Feb 19, 2021

For future readers, please see the documentation here.

Closed due to inactivity, please reopen if needed.

Top Results From Across the Web

How to Increase Request Timeout in NGINX - Ubiq BI

By default, NGINX request timeout is 60 seconds. Sometimes you may need to increase request timeout in NGINX to serve long-running requests.

Nginx reverse proxy causing 504 Gateway Timeout

I am using Nginx as a reverse proxy that takes requests then does a proxy_pass to get the actual web application from the...

Module ngx_http_proxy_module - Nginx.org

Defines a timeout for establishing a connection with a proxied server. It should be noted that this timeout cannot usually exceed 75 seconds....

Adjusting nginx-proxy Timeout Configuration - SSDT Wiki

This sets a 300 second (5 minute) timeout for most timeouts and 90 minutes for read-timeout. The read-timeout may seem excessive. However, when ......

How to Increase Request Timeout in NGINX - TecAdmin

Sometimes the long running requests failed with the error message “504: Gateway Timeout” in NGINX web server. To solve this issue, ...