Selfhosted

40183 readers

540 users here now

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:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

198

Dashboard for my current homelab setup (lemmy.world)

submitted 1 year ago* (last edited 1 year ago) by Gubb@lemmy.world to c/selfhosted@lemmy.world

29 comments fedilink hide all child comments

Pretty happy with how my homelab is coming along!

you are viewing a single comment's thread
view the rest of the comments

[–] macstainless@discuss.tchncs.de 4 points 1 year ago (4 children)

How did you get it to connect to your Pi? I’m hitting a lot of issues on that.

I’m running homepage in Docker and my pi is another machine on my network. But the container doesn’t see the Pi at all. Can you provide any insight?

[–] Gubb@lemmy.world 4 points 1 year ago* (last edited 1 year ago) (3 children)

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 1 points 1 year ago (2 children)

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.world 1 points 1 year ago (1 children)

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 1 points 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.