Hi folks,
Just set up Nginx Proxy Manager + Pihole and a new domain with Porkbun. All is working and I have all my services service.mydomain.com, however some services such as pihole seem to be strictly reachable with /admin at the end. This means with my current setup it only directs me to pihole.mydomain.com which leads to a 403 Forbidden.
This is what I have tried, but with no prevail. Not really getting the hang of this so would really appriciate a pinpoint on this :)
Side question: Are you exposing your pihole externally?
nope. Been using Tailscale to acesss my stuff from home.
Add the following in Advanced tab
location / { return 301 /admin;}location /admin { proxy_pass [url=http://<Pi-hole-IP>:<Pi-hole-Port>/admin;]http://<Pi-hole-IP>:<Pi-hole-Port>/admin;[/url] proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Forwarded-Proto $scheme;}
replace the IP and port
Thank you for providing this, however when i now browse to pihole.mydomain.com it gives me a 404, and the URL is directed to pihole.mydomain.com/admin:8118. E.g. the port is somehow ending up at the end of the url haha.
@Sunny' 🌻 that must not happen, did you remove the custom location from before? The above is working with my pihole setup
Ahhh i got it working now! Thanks a bunch for the help, been trying to get this to work for hours now hehe
Just tried this myself and mine does the same thing but I don't have anything set in the custom locations tab. What did you do to resolve it?
Remove any custom locations (if u have tried to add any), and then simply copy paste this into the advanced tab. Dont forget to change the <IP+PORT>
location / {
return 301 /admin;
}
location /admin {
proxy_pass http://<YOUR IP:PORT>/admin;
proxy_set_header Host $host;
proxy_set_header X-Real-IP $remote_addr;
proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
proxy_set_header X-Forwarded-Proto $scheme;
}
Let me know how it goes :)
Yeah that's exactly what I'd done but it was insisting on trying to redirect me to the site on port 4443 for some reason.
Fixed it in the end by reverting the NPM config to default (no advanced settings) and instead using Pihole's VIRTUAL_HOST=pihole.mydomain.internal environment variable in the Docker compose file.
Cheers for your help anyway!
If you're going to be playing with custom locations and such, it might be worth using nginx directly instead of through the limitations of NPM.
code formatting is messed up :/
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
No trolling.
Resources:
Any issues on the community? Report it using the report flag.
Questions? DM the mods!