Selfhosted

40382 readers

467 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 2 years ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

My first try at self hosting, and I have some questions... (lemmy.dbzer0.com)

submitted 1 month ago by Polite_Crocodile@lemmy.dbzer0.com to c/selfhosted@lemmy.world

14 comments fedilink hide all child comments

So, here's what I set up:

Docker with some containers behind Gluetun

Gluetun gives access to the local network so I can access the containers on my home network through http.

The only port I exposed to the internet is the 32400 for Plex.

I reach my home network remotely only through Wireguard, my fritzbox router has a guided setupt that gives me a wg configuration so I just scanned the QR code with my phone. I learned this opens the default wg port.

Now, you can never be 100% safe, but is my simple setup safe/solid enough?

9 times out of 10 I thinker with it when I am at home

It's still a work in progress and I am open to any kind of suggestions

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

[–] just_another_person@lemmy.world 1 points 1 month ago (2 children)

Honestly, you're just making more limitations and overhead by running everything over tunnels locally. There are better ways to secure your local network. If this works for you, and you don't want to bother with extra steps, just go for it though.

The downsides are performance, and a lot of extra hurdles trying to get other things to interface with any of the other services.

You'll also be at a disadvantage coming to forums and asking for help, because the preface will be explaining your setup before anyone can really help you with issues.

[–] Polite_Crocodile@lemmy.dbzer0.com 1 points 1 month ago (1 children)

Maybe I asked the wrong question. I meant to ask: this is what I came up with. It works. Some containers in docker and the only open ports are the Wireguard one and Plex. Is it safe to have everything on http inside my home network or should I look into hardening it?

[–] just_another_person@lemmy.world 2 points 1 month ago* (last edited 1 month ago)

Well the service doesn't matter. The authentication and authorization to the service does. If whatever you're running has a solid barrier to entry, then no problems. If it's open without any challenges, AND it can perform actions that harm your network, then that's bad news.

If you're worried about someone getting into your network and hacking something, the tunnels won't do much to prevent that. What you're describing is Security Through Obscurity in a way. You're putting up extra unnecessary barriers that aren't preventing access to something that isn't secure in the first place.