Selfhosted

46672 readers

1726 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

355

Come to say thank you. Time to move from proprietary to Open Source (lemmy.world)

submitted 3 days ago by essell@lemmy.world to c/selfhosted@lemmy.world

83 comments fedilink hide all child comments

Thanks to this community I've learned and I'm feeling inspired. I've loved having an NAS for the last few years, but it's woefully under powered for what I'm using it for these days.

So I've ordered some basic PC parts, gonna build a basic setup using an old CPU I got lying about and try the NAS OS I saw talked about on here recently.

TrueNAS looks like a good option with only slight fears it'll go down the well known path to the dark side like so many free options before.

In any event, I'm looking forward to adding Nextcloud and Jellyfin, to trying out Docker and generally having more control over things.

Thanks again to you all for informing and inspiring.

I'll be back if I get questions!

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

[–] dan@upvote.au 10 points 3 days ago* (last edited 3 days ago) (2 children)

Don't. Use a VPN like Tailscale or Wireguard. Tailscale uses the Wireguard protocol but it's very easy to configure, and will automatically set up a peer-to-peer mesh network for you (each node on the VPN can directly reach any other node, without having to route through a central server).

The only things that should be exposed publicly are things that absolutely need to be - for example, parts of Home Assistant need to be publicly exposed if you use the Google Assistant or Alexa integrations, since Google and Amazon need to be able to reach it.

[–] randint@lemmy.frozeninferno.xyz 1 points 1 day ago (1 children)

Offtopic, but do you think it's better to use HTTPS for non-public web services that must be accessed through ssh?

[–] dan@upvote.au 2 points 1 day ago* (last edited 1 day ago)

I usually use HTTPS, because a lot of web features only work over HTTPS.

You can use Let's Encrypt DNS challenges to get real TLS certificates for internal hosts, instead of having to use your own CA or self-signed certificates.

[–] possiblylinux127@lemmy.zip 0 points 2 days ago (1 children)

One thing to note: the NAT traversal doesn't always work especially for symmetric NAT. If you want reliable p2p connections I would setup IPv6

[–] dan@upvote.au 3 points 2 days ago* (last edited 2 days ago)

Tailscale has several NAT bypass / hole punching methods for double NAT (including CGNAT) and symmetric NAT, but they don't work in 100% of cases. https://tailscale.com/blog/how-nat-traversal-works

IPv6 is definitely a good solution since then you don't have to deal with NAT at all. IPv6 is pretty easily doable in the USA (at long as you're not using Starlink) but can be harder in other countries that don't have as robust IPv6 infrastructure.