Selfhosted

40324 readers

309 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

Are you exposing any ports on your home server? (lemmy.world)

submitted 1 year ago by fhein@lemmy.world to c/selfhosted@lemmy.world

105 comments fedilink hide all child comments

Maybe I'm using the wrong terms, but what I'm wondering is if people are running services at home that they've made accessible from the internet. I.e. not open to the public, only so that they can use their own services from anywhere.

I'm paranoid a f when it comes to our home server, and even as a fairly experienced Linux user and programmer I don't trust myself when it comes to computer security. However, it would be very convenient if my wife and I could access our self-hosted services when away from home. Or perhaps even make an album public and share a link with a few friends (e.g. Nextcloud, but I haven't set that up yet).

Currently all our services run in docker containers, with separate user accounts, but I wouldn't trust that to be 100% safe. Is there some kind of idiot proof way to expose one of the services to the internet without risking the integrity of the whole server in case it somehow gets compromised?

How are the rest of you reasoning about security? Renting a VPS for anything exposed? Using some kind of VPN to connect your phones to home network? Would you trust something like Nextcloud over HTTPS to never get hacked?

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

[–] effingjoe@kbin.social 52 points 1 year ago (12 children)

I think many of use are using reverse proxies, and opening port 443 (https) and maybe port 80 (http).

[–] housepanther@lemmy.goblackcat.com -2 points 1 year ago (11 children)

Port forwarding can be a recipe for disaster. I'd much rather make use of reverse proxying.

[–] thomcat@powerg.love 4 points 1 year ago (1 children)

@housepanther @effingjoe Unless you're running a router/firewall on the edge that can act as a reverse proxy, you kind of need to port forward to a reverse proxy if you're behind NAT.

[–] housepanther@lemmy.goblackcat.com 1 points 1 year ago (1 children)

You could use a VPS as a proxy and set up a VPN tunnel between the home server and the VPS to avoid port forwarding altogether. I do this for my mastodon and lemmy instances. My home server is of course behind NAT but there's no need for any kind of port forwarding. I should know because I have none configured.

[–] SeeJayEmm@lemmy.procrastinati.org 1 points 1 year ago

At that point why don't you just run it in the vps and save the hop.

load more comments (9 replies)