Selfhosted

60114 readers

1118 users here now

A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.

Rules:

Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
No spam.
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
Submission headline should match the article title.
No trolling.

Resources:

selfh.st Newsletter and index of selfhosted software and apps
awesome-selfhosted software
awesome-sysadmin resources
Self-Hosted Podcast from Jupiter Broadcasting

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 3 years ago

MODERATORS

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

How to setup my own home server and make it available to anyone? (slrpnk.net)

submitted 2 years ago* (last edited 2 years ago) by khoi@slrpnk.net to c/selfhosted@lemmy.world

41 comments fedilink hide all child comments

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?

you are viewing a single comment's thread
view the rest of the comments

[–] BearOfaTime@lemm.ee 35 points 2 years ago (1 children)

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 2 points 2 years ago (1 children)

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 1 points 2 years 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.