Hello Selfhosted peeps!

So I just got Traefik v3 setup inside my docker environment, and successfully got SSL certs for my services hosted within docker. However, I have an external device hosting PiHole and Wireguard-UI. I am looking to use the docker instance of Traefik v3 to obtain SSL certs for the internal use only for PiHole and Wireguard-UI.

I am still new to Traefik, and have no idea if this is possible, or how I would go about doing this.

Any tips, suggestions, links to documentation; I am all ears.

Video

Notes for above video

These 2 resources I utilized to help further my understanding.

Thank you

  • Hellmo_luciferrari@lemm.eeOP
    link
    fedilink
    English
    arrow-up
    0
    ·
    4 months ago

    I hate to report back, but something isn’t quite working for pihole behind Traefik.

    running “docker logs traefik” returns no error, and yet no certificate was presented to my pihole.

    Not sure what else I might be missing or that I might have wrong.

    • IHawkMike@lemmy.world
      link
      fedilink
      English
      arrow-up
      0
      ·
      4 months ago

      Can you see the router and service in the Traefik dashboard and do they show any errors there?

        • IHawkMike@lemmy.world
          link
          fedilink
          English
          arrow-up
          0
          ·
          4 months ago

          If you’re sure you’ve got a DNS entry for the Pihole FQDN pointing at Traefik, open the dev panel in your browser (F12), switch it to the Network tab, and visit the pihole URL.

          See if you get anything back and especially take note of the HTTP status codes.

          • Hellmo_luciferrari@lemm.eeOP
            link
            fedilink
            English
            arrow-up
            0
            ·
            4 months ago

            I will likely have to do some tinkering, and more reading up on this from the documentation I am thinking. I am getting HTTP 200 statuses basically across the board. When going to the FQDN it doesn’t redirect to the PiHole admin page like I was expecting. Again, likely some configuration that I have wrong.