Selfhosted

40226 readers

1122 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

109 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

[–] witten@lemmy.world 1 points 1 year ago (8 children)

Why not use Wireguard from your phones all the time, even at home? Just performance?

[+] somedaysoon@lemmy.world 2 points 1 year ago* (last edited 11 months ago) (7 children)

[deleted]

[–] witten@lemmy.world 2 points 1 year ago (6 children)

I don't know about your particular use case, but I've found that some apps experience problems when the IP address of a resource they're using changes out from under them. Like either they experience temporary connectivity issues during the transition or even just stop being able to reach the resource until restarted. However if your setup is working for you, that's great!

[–] a1studmuffin@aussie.zone 1 points 1 year ago (1 children)

I'm confused why the IP address of a resource is changing for you when you're moving in/out of the wireguard tunnel? In my setup the LAN IP addresses always stay the same whether I'm on the local network or accessing remotely, It's just the route to them that changes (over a different ethernet adapter). Perhaps that's what you meant, or there's some crazy configs out there I'm unaware of.

[–] witten@lemmy.world 1 points 1 year ago* (last edited 1 year ago)

I fully admit I may be doing this wrong. But in order to connect to a server over Wireguard I'm connecting to it over its Wireguard IP address. (And if I'm not connecting to it over Wireguard I don't connect to it over a Wireguard IP address.) It's relevant to note that I'm not using Wireguard as a traditional VPN where all traffic bound for the internet is tunneled over Wireguard. Instead, I'm using it strictly for point-to-point tunneling from a client to one of my servers. In other words, my default routes don't go to Wireguard. Maybe that's the difference here?

load more comments (4 replies)