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.

  • @TheButtonJustSpinsEnglish
    20•7 months ago

    You’ll want a reverse proxy like Traefik, Caddy, or nginx in order to get everything onto 80 or 443, and you’ll want to use your pihole to point domains/subdomains to your NAS.

    • adONisEnglish
      5•7 months 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

      • @rambos@lemm.eeEnglish
        3•7 months 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

      • @druidjaidan@lemmy.worldEnglish
        2•7 months 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.

        • adONisEnglish
          1•7 months ago

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

          • @druidjaidan@lemmy.worldEnglish
            1•7 months 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

            • adONisEnglish
              1•7 months 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”

      • @soundimus@lemmy.worldEnglish
        1•7 months ago

        Sorry for the silly questions but I’m new to this and still learning how this stuff works. Is there a guide for noobs to do this that you’re aware of? I own a domain and I’m trying to do exactly this.

        Also, would you recommend traefik over nginx? I am told that if I want to use the skills in a professional environment I should learn nginx but I’ve read it doesn’t have an interface and the configuration is manual.

        I’ve got pterodactyl running some game servers locally I’d like to open to my friends and this should be a secure way to do this.

        I also read below I should use a DNS if I don’t have a static IP. Does that throw a wrench in all this?

        • adONisEnglish
          2•7 months ago

          I don’t know of any beginner tutorial, since I learned it along the way.

          But in a nutshell. Most webservers (reverse proxies) are manual. nginx, caddy, traefik. However, there’s nginx proxy manager, which is a web gui.

          Regarding DNS, you need DNS regardless of fixed IP what you probably mean is dynDNS (dynamic dns) which you’ll definitely need if your IP changes.