Greetings! I currently host a number of services on an old pc in my basement. I have ports 80 and 443 forwarded and am running Nginx Proxy Manager as well as Authelia to protect most of them. I have set up a lemmy instance that I am using as my main point of access to the fediverse. I guess I have two questions. I am assuming that hiding lemmy behind Authelia would break Federation (although maybe only one way?), is that correct? And secondly, would it be objectively safer for me to pay for a VPS, run Nginx Proxy Manager there and then forward all of the traffic to the services hosted in my basement server using Tailscale? Thanks!

  • curioushom@lemmy.one
    link
    fedilink
    English
    arrow-up
    3
    ·
    1 year ago

    Not sure about the Lemmy part of the question… but it’ll definitely be safer to run nginx on a VPS and then communicate with your basement box over tailscale. That doesn’t expose your home ip for your services. The other thing you can look into is using a wildcard cert so the specific services you’re ruining aren’t enumerated in your DNS, might not be necessary since you have nginx sitting in front.

    • El Gringo Loco@lemmy.donmcgin.comOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Thank you! I have a followup question if you don’t mind. If I host npm on a vps that allows me, say 500GB of data transfer a month, and I am streaming media through a jellyfin instance that I have forwarded through the VPS, will the media I’m streaming count against that transfer amount? This seems like basic information that I should have learned a long time ago.

      • jackz@lemmyrs.org
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 year ago

        I think that depends on if the VPS charges incoming and outgoing external connections, some only charge outgoing. From VPS to browser would be outgoing, from your home instance to VPS would be incoming.

      • curioushom@lemmy.one
        link
        fedilink
        English
        arrow-up
        1
        ·
        1 year ago

        Like the other poster said, the traffic will go through the VPS. But since you mentioned tailscale, why not just connect to your network over tailscale. You could even use DNS to point to your services (nicer names than IPs) but then the clients would connect directly and you wouldn’t need to route through VPS.

        • El Gringo Loco@lemmy.donmcgin.comOP
          link
          fedilink
          English
          arrow-up
          3
          ·
          1 year ago

          I’ve definitely thought about it, and I would if it were just me. I share some services with family and I don’t want to be responsible for troubleshooting if they accidentally uninstall tailscale or reset their phones

  • cstine@lemmy.uncomfortable.business
    link
    fedilink
    English
    arrow-up
    1
    ·
    1 year ago

    NPM also looks abandoned right now. There’s some security patches that are not being addressed, and certificate renewal is hit or miss due to the age of NPM’s certbot vs the mainline.

    If you’re deploying something new, you might want to consider caddy or nginx by itself or some other reverse proxy at this point since it really looks like the dev has vanished and nobody is taking over maintenance yet.

    • El Gringo Loco@lemmy.donmcgin.comOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      1 year ago

      Are you sure it’s abandoned? The docker page was last updated three days ago and there is activity on the github page. Are they just updating the software without pushing any security fixes? I’ve definitely not had issues renewing certificates

      • cstine@lemmy.uncomfortable.business
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        There are nearly 1000 open issues and a couple of them are about potential vulnerabilities where the repeated refrain is ‘we tried to contact the developer, but there’s no response’ which makes me… uncomfortable, especially given that NPM was the gatekeeper to a lot of services on my local network.

        The cert error is related to outdated python code in the latest shipping version, https://github.com/NginxProxyManager/nginx-proxy-manager/issues/2912 and 2921.

        Again, you CAN work around it but the whole radio silence on issues and ongoing issues just makes me uncomfortable with the project and exceedingly reluctant to continue using it because it’s unclear what’s going on, and why.

        • El Gringo Loco@lemmy.donmcgin.comOP
          link
          fedilink
          English
          arrow-up
          1
          ·
          1 year ago

          Thank you for explaining and for the examples, it’s definitely time to start learning caddy. I liked npm for the simple gui, but security and reliability are more important