Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

502 Bad Gateway- NGiNX / uWSGI / Django #682

Closed
pnovotnak opened this issue Aug 10, 2014 · 4 comments
Closed

502 Bad Gateway- NGiNX / uWSGI / Django #682

pnovotnak opened this issue Aug 10, 2014 · 4 comments

Comments

@pnovotnak
Copy link

I see lots of the following in my logs, and get complaints from users of the website when working in the site's Django admin:

recv() failed (104: Connection reset by peer) while reading response header from upstream, client

I've tried lots of things, and actually found a descriptor leak in the codebase, but nothing so far has helped. I've just applied a buffer size increase, and I'll report back if it solves he issue.

It's a large site, and there are a lot of third party modules that set cookies. I count 24 of them, if that makes a difference.

@svenstaro
Copy link

Maybe try the mailing list or IRC instead? Pretty sure this is not a bug in uwsgi.

@pnovotnak
Copy link
Author

Setting buffer-size = 65535 solved this for us.

@kishan3
Copy link

kishan3 commented Jul 7, 2016

@pnovotnak In which file to set this. can you tell?

@tiantaozhang
Copy link

because the default buffer-size is 4k, buffer-size = 65535 solved for me too

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants