mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-26 01:45:54 +03:00
[GH-ISSUE #1056] Error 502 - Bad gateway - Connection reset by peer) while reading response header from upstream #884
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#884
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 @redtripleAAA on GitHub (May 2, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1056
Checklist
jc21/nginx-proxy-manager:latestdocker image?Yes
Yes
Describe the bug
A clear and concise description of what the bug is.
Getting Error 502 - Bad gateway - Connection reset by peer) while reading response header from upstream
When using network service mode of two containers in a single docker compose stack
What version of Nginx Proxy Manager is reported on the login page?
v2.8.1 © 2019 jc21.com
To Reproduce
Here is the stack I have that is not working
Expected behavior
To launch the web service GUI through the proxy hostname
Operating System
Synology NAS DSM'
Docker
Portainer
Additional context
I have another host that is working fine almost same setup
I can access the container without issues using private IP + Port internally (
http://10.0.12.16:8228) but not through proxy managerLogs
From:
/config/log/error.logNot working
Working VPN port
From:
/config/log/proxy_host-63.logPlease let me know what you think.
Thanks in advance!
@redtripleAAA commented on GitHub (May 2, 2021):
Update:
After I ran the following commands to do some clean up and restarted Docker host (Synology NAS)
docker image prune -adocker network pruneIt worked and now I am not longer getting the Bad Gateway error page.