46
Need help: accessing all my containers by name (yall.theatl.social)
submitted 2 years ago by to c/selfhosted@lemmy.world
34 comments fedilink hide all child comments
 

I’m to the point now where my little home device has enough services and such that bookmarking them all as http://nas-address:port is annoying me. I’ve got 3 docker stacks going on (I think) and 2 networks on my Synology. What’s the best or easiest way to be able to reach them by e.g. http://pi-hole and such?

I’m running all on a Synology 920+ behind a modem/router from my ISP so everything is on 192.168.1.0/24 subnet, and I’ve got Tailscale on it with it as an exit node if that helps.

you are viewing a single comment's thread
view the rest of the comments
[–] 2 points 2 years ago (1 child)

Or just a dynamics dns service like duckdns. Point a CNAME at your duckdns name. Or better still, a cron running locally and updating cloudflare dns etc. Lots of better options for home hosting than hoping your ip stays static.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    By hopefully... I actually meant that OP might have a static IP already.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago (1 child)

    Sorry I read "hopefully" as an imperative. At least in the US static home IPs are very rare so I generally assume some form of DDNS will be needed for any home hosting solution

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 2 child comments
    •
  • [–] 1 point 2 years ago

    Wher I live they are rare too. They used to be more common back in the days, but now they're mostly offered to business customers.

    But you're right.. the "hopefully" could've been easily misinterpreted as in "hoping the IP doesn't change anytime soon, or ever"

  • permalink
  • fedilink
  • source
  • parent