starred/nginx-proxy-manager-NginxProxyManager

Fork 0

mirror of https://github.com/NginxProxyManager/nginx-proxy-manager.git synced 2026-04-25 17:35:52 +03:00

[GH-ISSUE #1027] Custom location #864

New issue

Closed

opened 2026-02-26 06:34:43 +03:00 by kerem · 4 comments

kerem commented

2026-02-26 06:34:43 +03:00

Owner

Originally created by @EvertJob on GitHub (Apr 18, 2021).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1027

Hi,

Maybe someone can help me.

I'm running Nginx Proxy and it works fine. The only problem: I'm running Pi-Hole on port 82 and I cannot get it working.
The URL I need to use for the admin is: http://192.168.1.254:82/admin. I would like to connect to pihole.domain.ext.

I've tried everything as far as I can see, can someone help me?

Originally created by @EvertJob on GitHub (Apr 18, 2021). Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/1027 Hi, Maybe someone can help me. I'm running Nginx Proxy and it works fine. The only problem: I'm running Pi-Hole on port 82 and I cannot get it working. The URL I need to use for the admin is: http://192.168.1.254:82/admin. I would like to connect to pihole.domain.ext. I've tried everything as far as I can see, can someone help me? <img width="535" alt="Screenshot 2021-04-18 at 20 03 53" src="https://user-images.githubusercontent.com/58138839/115155640-35df8b00-a081-11eb-967c-a9783aa30ded.png"> <img width="531" alt="Screenshot 2021-04-18 at 20 04 12" src="https://user-images.githubusercontent.com/58138839/115155663-40018980-a081-11eb-8222-f2c0775dfbfd.png">

kerem

2026-02-26 06:34:43 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 06:34:44 +03:00

Author

Owner

@dgsharpe commented on GitHub (Apr 19, 2021):

Check out these instructions posted by @jc21 in #104 and make sure you've followed them exactly:

Create a proxy host

On the details tab, enter any ip address and port, it's required for the form but it won't actually be used, so it can be anything

On the Custom Locations tab, create a location with / as the location path and for the Forward Hostname / IP enter 192.168.0.10/phpmyadmin/ making sure you have that trailing slash, it's important.

Save, and test.

In particular, it looks like you might have not included the trailing slash in step 3.

However, this Github issues page isn't really for community support, it's for reporting bugs - if you're looking for assistance with your setup, you'll be better off checking out the Reddit community.

@dgsharpe commented on GitHub (Apr 19, 2021): Check out these instructions posted by @jc21 in #104 and make sure you've followed them exactly: >1. Create a proxy host >2. On the details tab, enter any ip address and port, it's required for the form but it won't actually be used, so it can be anything >3. On the Custom Locations tab, create a location with / as the location path and for the Forward Hostname / IP enter 192.168.0.10/phpmyadmin/ making sure you have that trailing slash, it's important. >4. Save, and test. In particular, it looks like you might have not included the trailing slash in step 3. However, this Github issues page isn't really for community support, it's for reporting bugs - if you're looking for assistance with your setup, you'll be better off [checking out the Reddit community.](https://www.reddit.com/r/nginxproxymanager/)

kerem commented

2026-02-26 06:34:44 +03:00

Author

Owner

@3Dscrewer commented on GitHub (Apr 20, 2021):

That’s not a bug, that happens not reading the manuals. The use of custom location is totally wrong. The custom location is needed if your pi-hole is in a subfolder. For example Tomcat war container. The standard installation is not. You have simply to use the IP, I guess raspberry, and the port. You must see a page like the picture, click at the blue colored sentence and you’re ready

Edit: Since pi-hole is normal for internal use, activate „Block common Exploits“ for a little bit security.

Last Edit: to go direct to admin page is a look like this. http://192.xxx.xxx.xxx:82/admin/
If you’re setup is working, use in browser http://your.domain.tld/admin/ and save as bookmark

@3Dscrewer commented on GitHub (Apr 20, 2021): That’s not a bug, that happens not reading the manuals. The use of custom location is totally wrong. The custom location is needed if your pi-hole is in a subfolder. For example Tomcat war container. The standard installation is not. You have simply to use the IP, I guess raspberry, and the port. You must see a page like the picture, click at the blue colored sentence and you’re ready Edit: Since pi-hole is normal for internal use, activate „Block common Exploits“ for a little bit security. Last Edit: to go direct to admin page is a look like this. http://192.xxx.xxx.xxx:82/admin/ If you’re setup is working, use in browser http://your.domain.tld/admin/ and save as bookmark ![346FBA4C-2033-4E86-9037-381FF65ADAD6](https://user-images.githubusercontent.com/34925249/115359899-675e7080-a1bf-11eb-9ee4-c1094f91b37e.png)

kerem commented

2026-02-26 06:34:44 +03:00

Author

Owner

@3Dscrewer commented on GitHub (Apr 21, 2021):

@EvertJob Sorry for that reading the manual, but Google is still your friend. I don’t use Pi-Hole over the Net, but I’m interested in this case.
So the path to the admin page is /var/www/html/admin. So the custom path is /html/admin/ because in /html is only the landing page like picture above.
The Web access doesn’t work at all, because Pi-hole is refusing the access. It is showing that picture, ok, whitelist and again, no access.
And here comes Google.

https://docs.pi-hole.net/guides/webserver/nginx/

So one possible way .... I didn’t try, because I don’t need that.
at /root/npm/data/nginx/proxy_host/ you will find
1.conf
2.conf
depending how many domains you have.
There you must find your domain, it is mentioned at the Top.
Copy necessary parts of the Pi-Hole site into that x.conf and it should work ... I guess 😉

Sorry for that, but is a security reason by Pi-hole.

@3Dscrewer commented on GitHub (Apr 21, 2021): @EvertJob Sorry for that reading the manual, but Google is still your friend. I don’t use Pi-Hole over the Net, but I’m interested in this case. So the path to the admin page is /var/www/html/admin. So the custom path is /html/admin/ because in /html is only the landing page like picture above. The Web access doesn’t work at all, because Pi-hole is refusing the access. It is showing that picture, ok, whitelist and again, no access. And here comes Google. https://docs.pi-hole.net/guides/webserver/nginx/ So one possible way .... I didn’t try, because I don’t need that. at /root/npm/data/nginx/proxy_host/ you will find 1.conf 2.conf depending how many domains you have. There you must find your domain, it is mentioned at the Top. Copy necessary parts of the Pi-Hole site into that x.conf and it should work ... I guess 😉 Sorry for that, but is a security reason by Pi-hole. ![3EEC73A1-8BB6-4FF5-963C-B855EB88F247](https://user-images.githubusercontent.com/34925249/115542479-9bf62900-a2a0-11eb-836f-9a1839e29bb7.jpeg)

kerem commented

2026-02-26 06:34:44 +03:00

Author

Owner

@EvertJob commented on GitHub (Apr 21, 2021):

@3Dscrewer Thanks. But the issue is now fixed. The last / was missing.

@EvertJob commented on GitHub (Apr 21, 2021): @3Dscrewer Thanks. But the issue is now fixed. The last / was missing.

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/nginx-proxy-manager-NginxProxyManager#864

No description provided.

Rows
Columns