Pretty happy with how my homelab is coming along!

  • Gubb@lemmy.worldOP
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    1 year ago

    Hey! IM going to post my config below, excuse the formatting if it comes out really messed up, im totally unsure how Lemmy is going to handle this.

    - Pihole:
        icon: pi-hole.png # This is the icon that will be displayed on the widget
        href: Link to your PiHole login # Optional, but makes the widget clickable
        description: DNS Server/Ad-Blocker # Description of the service
        ping: IP_ADDRESS_PIHOLE # Options, but will ping the host and display latency
        widget:
            type: pihole # This is required by Homepage to define the type of widget 
            url: http://IP_ADDRESS_PIHOLE
            key: REDACTED # This is an API key generated on the PiHole
    

    Here is the link I used for obtaining the API key. https://pi-hole.net/blog/2022/11/17/upcoming-changes-authentication-for-more-api-endpoints-required/#page-content

    Let me know if you have any issues!

    • macstainless@discuss.tchncs.de
      link
      fedilink
      English
      arrow-up
      0
      ·
      1 year ago

      Thanks. I’ve done this (even getting my API key) but the issue I’m running into is the fact that the Docker container doesn’t see the Pi-Hole machine. I believe it’s a networking issue, but I don’t know how to figure out how to get it to see it. Is there a networking flag I need to include in Homepage’s Docker Compose? That seems to be my issue.

      • Gubb@lemmy.worldOP
        link
        fedilink
        English
        arrow-up
        0
        ·
        1 year ago

        Im not sure, I am also running Homepage in a docker container, I am able to connect to my pi-hole just fine. From the information I have, it seems like a networking issue.

        • macstainless@discuss.tchncs.de
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          I agree it’s a networking problem. The issue I have is I don’t know how to fix it.

          I installed Portainer and figured out how to get the container onto my network. But then it was unreachable. So I’m more lost the more I try to figure this out.

          Are you using any specific network commands in your docker compose? Are you running specific networking in the container? I’m trying to figure out how it’s working for you and what likely obvious thing I’m missing. Thanks.