mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 09:55:51 +03:00
[GH-ISSUE #438] 502 Bad Gateway due to proxy buffer size #369
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#369
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @damianog on GitHub (May 30, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/438
I am using
jc21/nginx-proxy-manager:latest2.3During POST action of an asp.net core Blazor application I get 502 error
from /data/logs/error.log I discovered the cause:
...upstream sent too big header while reading response header from upstream...I found the solution by configuring the Custom Nginx Configuration on "Advanced" tab with the following parameters:
as explained on http://nginx.org/en/docs/http/ngx_http_proxy_module.html#proxy_buffer_size
Please consider to add these parameters by default or make them configurable by panel settings.
@MartinKuhl commented on GitHub (Mar 3, 2021):
@damianog could you post your full entry in the Advanced tab?
@damianog commented on GitHub (Mar 3, 2021):
Hi @MartinKuhl,
cut and paste exactly as I wrote
@MartinKuhl commented on GitHub (Mar 4, 2021):
thanks a lot, that fixes my issue too!
@douglas1dev commented on GitHub (Oct 21, 2024):
thanks a lot