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!

  • bizdelnick@lemmy.mlEnglish
    11·
    15 days ago

    If you mean HTTP server, what you need is a reverse proxy and name-based virtual hosts. I usually use nginx for such tasks, but you may choose another web server that has these features.

  • skankhunt42@lemmy.caEnglish
    8·
    15 days ago

    Router gets the public IP. Login to it, find port forwarding option. You’ll pick a public port. IE 443 and forward it to a local IP:port combo, IE 192.168.0.101:443.

    Then you can pick another public port and forward it to a different private IP:port combo.

    If you want a subdomain, you forward one port to one host and have it do the work. IE configure Nginx to do whatever you want.

    EDIT: or you use IPv6. Everything is a public IP.

  • Nate066@lemmy.worldEnglish
    113·
    15 days ago

    VPN is definitely the way to go for home networks. Your router even has one built in. OpenVPN and Wireguard are good.

    If you really want to expose stuff like this the proper way is to isolate your home network from your internet exposed network using a VLAN. Then use a reverse proxy, like caddy and place everything behind it.

    Another benefit of a reverse proxy is you don’t need to setup https certs on everything just the proxy.

    You do need a business or prosumer router for this though. Something like Firewalla or setting up a OpenWRT or OPNsense.

    Synology also has there quick connect service as well. While not great if you keep UPNP off and ensure your firewall and login rate limiting is turned on it may be better then just directly exposing stuff. But its had its fair share of problems so yeah.

    Consider not self hosting everything. For example if all your family cares about is private photo storage, consider using a open source E2EE encrypted service for photos on the cloud like Ente Photos. Then you can use VPN for the rest. https://www.privacyguides.org/ has some recommendations for privacy friendly stuff.

    Also consider the fallout that would happen if you are hacked. If all your photos and other things get leaked because your setup was not secure was it really any better than using big tech?

    If nothing else please tell me you are using properly setup https certs from Let’s Encrypt or another good CA. Using a firewall and have login rate limiting setup on everything that is exposed. You can also test your SSL setup using something like https://www.ssllabs.com/ssltest/

    • Allero@lemmy.todayOPEnglish
      3·
      15 days ago

      No truly private photos ever enter the NAS, so on that front it should be fine.

      VPN is not an option for several reasons, unfortunately.

      But I do have a Let’s Encrypt certificate, firewall and I ban IP after 5 unsuccessful login attempts. I also have SSH disabled completely.

      SSL Test gave me a rating of A

  • towerful@programming.devEnglish
    8·
    15 days ago

    Who is externally reaching these servers?
    Joe public? Or just you and people you trust?

    If it’s Joe public, I wouldn’t have the entry point on my home network (I might VPS tunnel, or just VPS host it).

    If it’s just me and people I trust, I would use VPN for access, as opposed to exposing all these services publicly

    • Allero@lemmy.todayOPEnglish
      4·
      15 days ago

      Just me and the people I trust, but there are certain inconveniences around using VPN for access.

      First, I live in the jurisdiction that is heavily restrictive, so VPN is commonly in use to bypass censorship

      Second, I sometimes access my data from computers I trust but can’t install VPN clients on

      Third, I share my NAS resources with my family, and getting my mom to use a VPN every time she syncs her photos is near impossible

      So, fully recognizing the risks, I feel like I have to expose a lot of my services.

    • Allero@lemmy.todayOPEnglish
      3·
      15 days ago

      Update: tried Caddy, love it, dead simple, super fast, and absolutely works!

    • Allero@lemmy.todayOPEnglish
      1·
      15 days ago

      For now just some experiments alongside NAS

      Planning to host Bitwarden, Wallabag and other niceties on the server, and then when I get something more powerful, spin up Minecraft server and stuff

    • Allero@lemmy.todayOPEnglish
      2·
      15 days ago

      I will eventually!

      But for all I understand, it is to put many services on one machine, and I already have a NAS that is not going anywhere

      • ddh@lemmy.sdf.orgEnglish
        1·
        15 days ago

        I’ve gone the other way. I used to run a Proxmox cluster, then someone gave me a Synology NAS. Now it’s rare that I spin up Proxmox and instead use a mix of VMs, containers and Synology/Synocommunity apps.

        • Allero@lemmy.todayOPEnglish
          1·
          15 days ago

          Interesting!

          But I don’t want to mix it too much. I do have a Docker on it with just some essentials, but overall I’d like to keep NAS a storage unit and give the rest to a different server.

          I treat NAS as an essential service and the other server as a place to play around without pressure to screw anything

  • pleksi@sopuli.xyzEnglish
    61·
    15 days ago

    I really feel like people who are beginners shouldnt play with exposing their services. When you set up Caddy or some other reverse proxy and actually monitor it with something like fail2ban you can see that the crawlers etc are pretty fast to find your services. If any user has a very poor password (or is reusing a leaked one) then someone has pretty open access to their stuff and you wont even notice unless you’re logging stuff.

    Of course you can set up 2FA etc but that’s pretty involved compared to a simple wg tunnel that lives on your router.

    • r0ertel@lemmy.worldEnglish
      1·
      15 days ago

      My mantra is “plan to be hacked”. Whether this is a good backup strategy, a read-only VM, good monitoring or serious firewall rules.

    • Allero@lemmy.todayOPEnglish
      1·
      14 days ago

      For now I’m only toying around, experimenting a little - and then closing ports and turning my Pi off. I do have my NAS constantly exposed, but it is solidly hardened (firewall, no SSH, IP bans for unauthorized actions, etc. etc.), fully updated, hosts no sensitive data, and all that is important is backed up on an offline drive.

  • Chewy@discuss.tchncs.deEnglish
    3·
    15 days ago

    If you go with IPv6, all your devices/servers have their own IP. These IPs are valid in your LAN as well a externally.

    But it’s still important to use a reverse proxy (e.g. for TLS).

    • Allero@lemmy.todayOPEnglish
      2·
      15 days ago

      Oh, nice! So I don’t have just one, but many external IPs, one for every local device?

      • Chewy@discuss.tchncs.deEnglish
        1·
        15 days ago

        Yes, even IPv4 was intended to give each device in the world their own IP, but the address space is too limited. IPv6 fixes that.
        Actually, each device usually has multiple IPv6s, and only some/one are globally routable, i.e. it works outside of your home network. Finding out which one is global is a bit annoying sometimes, but it can be done.

        Usually routers still block incoming traffic for security reasons, so you still have to open ports in your router.

  • SmokeyDope@lemmy.worldEnglish
    2·
    15 days ago

    Good to hear you figured it out with router settings. I’m also new to this but got all that figured out this week. As other commenters say I went with a reverse proxy and configured it. I choose caddy over nginx for easy of install and config. I documented just about every step of the process. I’m a little scared to share my website on public fourms just yet but PM me ill send you a link if you want to see my infrastructure page where I share the steps and config files.

    • Allero@lemmy.todayOPEnglish
      1·
      15 days ago

      Thanks, I will! Wise of you not to share it publicly for security reasons

  • thelittleblackbird@lemmy.worldEnglish
    2·
    15 days ago

    If you have a prosumer router I suggest you to use the ddns in the router plus a reverse proxy. This would be the cleanest solution.

    If you can not, once everything is working with your external access to the synology, the dsm has a built-in reverse proxy so it can redirect http requests to another server. Although this proxy is really simple and limited it can get the work done if you setup is simple enough.

  • Onomatopoeia@lemmy.cafeEnglish
    1·
    15 days 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.

    • Allero@lemmy.todayOPEnglish
      1·
      15 days 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.worldEnglish
        1·
        15 days 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?