I’m pretty new to selfhosting and homelabs, and I would appreciate a simple-worded explanation here. Details are always welcome!

So, I have a home network with a dynamic external IP address. I already have my Synology NAS exposed to the Internet with DDNS - this was done using the interface, so didn’t require much technical knowledge.

Now, I would like to add another server (currently testing with Raspberry Pi) in the same LAN that would also be externally reachable, either through a subdomain (preferable), or through specific ports. How do I go about it?

P.S. Apparently, what I’ve tried on the router does work, it’s just that my NAS was sitting in the DMZ. Now it works!

  • Onomatopoeia@lemmy.cafe
    link
    fedilink
    English
    arrow-up
    1
    ·
    13 hours ago

    You’ll need to direct that port for the given service in the router control panel.

    For your current server you have a port forwarding for that port already. Just add a port forwarding rule for the new service.

    • AlleroOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      edit-2
      12 hours ago

      Tried doing that - here’s how I’ve set it up:

      Expected behavior: now when I enter <my domain>:8100, I reach 192.168.0.113:81

      Real behavior: connection times out

      • rtxn@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        edit-2
        12 hours ago

        Stupid question, but is the service reachable at all? What if you map 81 to 81? Or whichever port the other, confirmed-to-work service uses? What if you map that other service to 8100?

        • AlleroOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          edit-2
          12 hours ago

          Reachable through LAN, but not by URL, even if I port 81 to 81

          P.S. Solved! NAS was sitting in the DMZ and this broke forwarding.