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.

  • adONis@lemmy.worldEnglish
    6·
    2 years ago

    To add to that… If OP owns a domain, they could issue an SSL cert for a subsain, like lab.example.com and point the A record to the (hopefully static) IP if the router, and port forward 443 to pihole

    • druidjaidan@lemmy.worldEnglish
      2·
      2 years ago

      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.

        • druidjaidan@lemmy.worldEnglish
          1·
          2 years ago

          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

    • rambos@lemm.eeEnglish
      2·
      2 years ago

      Or if OP doesnt own a domain they could just use any custom word like jellyfin.op

      Also having nice homepage is usefull. I prefer homepage