Selfhosted

40347 readers

358 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 posting.
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Why VPN tunnels are safer than opening a port on my router? (programming.dev)

submitted 6 months ago* (last edited 6 months ago) by cheddar@programming.dev to c/selfhosted@lemmy.world

35 comments fedilink hide all child comments

Hi!

I often read suggestions to use something like Tailscale to create a tunnel between a home server and a VPS because it is allegedly safer than opening a port for WireGuard (WG) or Nginx on my router and connecting to my home network that way.

However, if my VPS is compromised, wouldn't the attacker still be able to access my local network? How does using an extra layer (the VPS) make it safer?

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

[–] BearOfaTime@lemm.ee 0 points 5 months ago* (last edited 5 months ago)

By learning before you take on the risk.

It's not like this isn't well documented.

If OP is asking this question, he's nowhere near knowledgeable enough to take on this risk.

Hell, I've been Cisco certified as an instructor since 1998 and I wouldn't expose a port. Fuck that.

I could open a port today, and within minutes I'll be getting hammered with port scans.

I did this about 10 years ago as a demonstration, and was immediately getting thousands of scans per second, eventually causing performance issues on the consumer-grade router.