mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #2091] Trying to point to npm itself to a sub domain #1506
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#1506
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 @denppa on GitHub (Jun 3, 2022).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2091
Checklist
jc21/nginx-proxy-manager:latestdocker image?Describe the bug
Installed npm using docker. Used compose to run it. Opened port 81 so I could configure it via ip:81. Now I have an admin account, I want to put it under my domain: npm.example.com Added wild card with the token in cloudflare.
Problem is I cannot appoint the correct proxy host for this to work.
Nginx Proxy Manager Version
v2.9.18
To Reproduce

Steps to reproduce the behavior:
Docker network list. Tried npm_default in the forward hostname, 127.0.0.1, localhost.
Expected behavior
Go to npm.example.com and see the npm login panel. I am met with error 520 instead.
Screenshots
Did include some.
Operating System
Ubuntu 20.04
Compose File:
Cloudflare DNS settings:

@denppa commented on GitHub (Jun 3, 2022):
Cloudflare IP address missed a number.