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 :)

  • Sunny' 🌻@slrpnk.netOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    3 days ago

    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' 🌻@slrpnk.netOP
        link
        fedilink
        English
        arrow-up
        3
        ·
        3 days ago

        Ahhh i got it working now! Thanks a bunch for the help, been trying to get this to work for hours now hehe

        • TedZanzibar@feddit.uk
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 hours ago

          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?

          • Sunny' 🌻@slrpnk.netOP
            link
            fedilink
            English
            arrow-up
            1
            ·
            2 hours ago

            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 :)

            • TedZanzibar@feddit.uk
              link
              fedilink
              English
              arrow-up
              1
              ·
              27 minutes ago

              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!

        • K3CAN@lemmy.radio
          link
          fedilink
          English
          arrow-up
          1
          ·
          22 hours ago

          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.