this post was submitted on 06 Jul 2023
198 points (97.1% liked)

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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

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

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

Pretty happy with how my homelab is coming along!

you are viewing a single comment's thread
view the rest of the comments
[–] 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.

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.