mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 17:35:52 +03:00
[GH-ISSUE #527] NPM does not proxy? #447
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#447
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 @R0yk3 on GitHub (Jul 28, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/527
Checklist
YES - Have you pulled and found the error with
jc21/nginx-proxy-manager:latestdocker image?NO - Are you sure you're not using someone else's docker image?
YES - If having problems with Lets Encrypt, have you made absolutely sure your site is accessible from outside of your network?
Describe the bug
With the proxy hosts enabeld i get no connection to the site. When i disable the proxy hosts i see the default congratulations from NPM.
So the dns points correct.
Ports are opend correct (port 80 and 443)
V 2.3.1
To Reproduce
Steps to reproduce the behavior:
Both pointed to the same ip.
Expected behavior
See a nginx welcome page.
Screenshots
dashboard
Operating System
debian 10 container on proxmox
Log files from data directory:
2020/07/28 09:41:08 [error] 9875#9875: *6171 upstream timed out (110: Operation timed out) while connecting to upstream, client: 84.105.86.217, server: test.sieliakus.nl, request: "GET / HTTP/1.1", upstream: "http://192.168.1.184:8080/", host: "test.sieliakus.nl" 2020/07/28 09:42:39 [error] 9875#9875: *6217 upstream timed out (110: Operation timed out) while connecting to upstream, client: 84.105.86.217, server: test.sieliakus.nl, request: "GET /favicon.ico HTTP/1.1", upstream: "http://192.168.1.184:8080/favicon.ico", host: "test.sieliakus.nl", referrer: "https://test.sieliakus.nl/" 2020/07/28 09:43:41 [error] 9875#9875: *6247 upstream timed out (110: Operation timed out) while connecting to upstream, client: 63.88.73.138, server: test.sieliakus.nl, request: "GET / HTTP/1.1", upstream: "http://192.168.1.184:8080/", host: "test.sieliakus.nl" 2020/07/28 09:46:28 [error] 10577#10577: *6336 upstream timed out (110: Operation timed out) while connecting to upstream, client: 84.241.203.139, server: test.sieliakus.nl, request: "GET / HTTP/1.1", upstream: "http://192.168.1.184:8080/", host: "test.sieliakus.nl" 2020/07/28 09:47:59 [error] 10577#10577: *6380 upstream timed out (110: Operation timed out) while connecting to upstream, client: 84.241.203.139, server: test.sieliakus.nl, request: "GET /favicon.ico HTTP/1.1", upstream: "http://192.168.1.184:8080/favicon.ico", host: "test.sieliakus.nl", referrer: "http://test.sieliakus.nl/"@s4b3rt0oth commented on GitHub (Jul 28, 2020):
Are you positive your DNS is setup correctly for this use-case?
@R0yk3 commented on GitHub (Jul 28, 2020):
Yes, you see the cloudflare IP adresses, not my home address.
But both pointing at the same ip wit a different outcome.
@s4b3rt0oth commented on GitHub (Jul 28, 2020):
If you're strictly allowing traffic only from Cloudflare, then that would explain why LetsEncrypt is unable to reach 84.105.86.217.
@R0yk3 commented on GitHub (Jul 28, 2020):
Wel, tested it with another domain name not behind cloudflare.
http://test.jeanineburgers.nl (point internal to nginx site, should be handeld by NPM, does not work)
https://test3.jeanineburgers.nl (points at same internal site as above but with https (not forced) should be handeld by NPM, does not work)
http://test2.jeanineburges.nl (no rule made for yet)(not handeld by NPM and works.
BTW, the letsencrypt certificate is given, so communication is happening. only npm is not 'forwarding'
Turned off dns routing by cloudflare, dut that does not make a difference..
@R0yk3 commented on GitHub (Jul 28, 2020):
Excuse me, i had UFW installed blocking everything. Turned it off now it works. Sorry for the screwup MYBAD...