Add proxy buffer size config to fix Bad Gateway #1984
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
To prevent `upstream sent too big header while reading response header from upstream` error
hubertdeng123
approved these changes
Feb 24, 2023
|
thanks for the PR! |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I was unable to access the
All Eventstab when looking at an issue. The browser showed an infinite loading screen. Devtools revealed 502 Bad Gateway responses for/api/0/issues/:id/attachments/. When I looked at the nginx log I found the following error:upstream sent too big header while reading response header from upstream.This PR fixes the bad gateway error and makes the
All Eventstab work again.Doesn't seem to be the only place affected by this issue either. I checked the logs for this specific error using
docker logs sentry-self-hosted-nginx-1 2>&1 | grep 'upstream sent too big header while reading response header from upstream'and found another instance of this issue on the/api/0/organizations/:name/sessions/endpoint, but no idea where this is used in the frontend.resolves #1927
Legal Boilerplate
Look, I get it. The entity doing business as "Sentry" was incorporated in the State of Delaware in 2015 as Functional Software, Inc. and is gonna need some rights from me in order to utilize my contributions in this here PR. So here's the deal: I retain all rights, title and interest in and to my contributions, and by keeping this boilerplate intact I confirm that Sentry can use, modify, copy, and redistribute my contributions, under Sentry's choice of terms.