I’d like to have my own server at home sorta like a home AWS.

How to set up one and make it available to anyone over the Internet? What tech specs should I buy (RAM, CPU, # of cores, operating system, etc.)?

How much does it cost to keep one running all the time?

  • BearOfaTime@lemm.ee
    link
    fedilink
    English
    arrow-up
    36
    arrow-down
    1
    ·
    8 months ago

    Generally speaking, not a well-advised idea, especially for someone who has to ask how to do it (truly not being snarky).

    I was a cisco instructor in the 90’s, (so teaching networking and security were my bread and butter for a while) and I wouldn’t think of doing this - except… If the only access was via a mesh network client such as Tails/Tailscale, the server was dedicated to just this purpose, it was isolated on its own LAN segment/DMZ with no routing path to my home network segment, the server was not Windows, but Linux, and I had a robust backup plan, access control plan, and access monitoring with alerts.

    There’s just too much risk exposing a port to the world.

    • picnicolas@slrpnk.net
      link
      fedilink
      English
      arrow-up
      2
      ·
      8 months ago

      If you’re only accessing the server remotely via Tailscale and no ports are open, is it necessary to have the server on its own isolated VLAN? I like accessing my server locally most of the time and via Tailscale when I’m out and about.

      • BearOfaTime@lemm.ee
        link
        fedilink
        English
        arrow-up
        2
        arrow-down
        1
        ·
        8 months ago

        I’d still do this.

        Security isn’t one thing, it’s layers. So if any single layer fails another still prevents access.

        With just Tails, if a bad actor gets access via a compromised user machine, they could potentially get access to the rest of your network. If the server is on an isolated Lan, there’s nothing for them to access - it’s a rock-solid guarantee that the most they can do is damage to that server and network segment.

        We (us IT folks) see users get compromised almost daily, largely through social engineering. It’s a huge risk.

        And it’s trivial to have something on its own Lan segment.