Issue Connecting to Nginx Proxy Manager Admin Portal
reddit / selfhosted

----------------------------------------------------------------------
MonstaHuntah · 2023-10-09 21:32

Hello,

I'm hitting an issue where it seems like the Nginx Proxy Manager isn't
supplying the correct subdomain --> port translation. When I try and
access the admin portal using the subdomain I've configured, it drops
me at the default NGINX page:

​

https://preview.redd.it/00wsenjiw8tb1.png?width=2328&format=png&auto=w
ebp&s=de27a3c4a2957da73f6c41455f960ac569bc781b

I'm currently using the following stack:

* Beelink server running Ubuntu 22.04.3
   * Pi-hole (running in a container) acting as local DNS, containing
two A/AAAA records:
      *  beelink.js-lan -->  192.168.0.106
      * npm.beelink.js-lan -->  [192.168.0.106](https://192.168.0.106)
   * Nginx Proxy Manager (running in a container)
      * See attached screenshot for configuration

[NPM Proxy Hosts](https://preview.redd.it/e1pe6intv8tb1.png?width=2398
&format=png&auto=webp&s=1c14adb29faa016b0381f3b21a325a7a9557e7b9)

​

Any help with this would be greatly appreciated!

----------------------------------------------------------------------
thekrautboy · 2023-10-09 22:51

> beelink.js-lan

Please stop making up TLDs for your homenetwork. `.js-lan`is not
valid. Use TLDs for private homenetwork usage that are meant for this,
such as `example.lan` or `example.private` or `example.home.arpa`

For your NPM question, why not ask in the ideal sub
/r/NginxProxyManager for support?

----------------------------------------------------------------------
MonstaHuntah · 2023-10-09 23:53

Thanks for the recommendation on the private TLDs, I hadn't heard of
that practice before (just getting started w/ the self-hosting).

I reworded the question a few times before posting, and I guess I
didn't realize how NPM heavy I went. I'll check over there.

----------------------------------------------------------------------
viktae · 2023-10-10 00:54

I'm myself kinda a noob in this field, but I wonder if the issue
doesn't lie in your records. Shouldn't  you only point the root domain
to that ip ? You shouldn't need to add that npm subdomain record,
since NPM will anyway handle all of that.

----------------------------------------------------------------------
thekrautboy · 2023-10-10 02:18

> Shouldn't you only point the root domain to that ip ?

Why? You can point as many domains as you want to the same IP.

> You shouldn't need to add that npm subdomain record, since NPM will
anyway handle all of that.

NPM doesnt handle any DNS at all. OP could consider adding a wildcard
CNAME record in order to redirect all non-existing subdomains to the
same host, assuming they are running most/all of their services from
the same Docker host IP. But if not, then each host that NPM should
"react" to needs to have its own domain or subdomain.

> By doing what you do, the subdomain will always point to port 80,
hence why you land on the default page, I think.

Subdomains, or domains, dont point to any ports, ever. NPM would do
that, indirectly.

----------------------------------------------------------------------
MrAlfabet · 2023-10-10 18:25

Have the target in npm as http://127.0.0.1:81

That should work.