mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #254] Internal DNS resolution Issue #224
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#224
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 @mspencerl87 on GitHub (Dec 11, 2019).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/254
I've come to the conclusion posted here
https://forums.unraid.net/topic/76460-support-djoss-nginx-proxy-manager/?do=findComment&comment=797477
That this is and issue with DNS resolution
All containers running under "Bridged" in docker 172.17.x.x
Example
Setting up proxyhosts
http://internalserver:80 -502 Bad Gateway - nginx
Using
http://172.17.0.7:80 - Page loads fine.
docker exec -it NginxProxyManager Sh
nslookup 172.17.0.7 "can't resolve does not resolve (null)
ping 172.17.0.7
PING 172.17.0.7 (172.17.0.7): 56 data bytes
64 bytes from 172.17.0.7: seq=0 ttl=64 time=0.048 ms
@mspencerl87 commented on GitHub (Dec 11, 2019):
The work around.. Was point to Unraid IP and use custom ports.. Ignoring hostnames...