this post was submitted on 18 Jul 2025

88 points (86.7% liked)

Selfhosted

selfhosted@lemmy.world

63,755 readers

5,189 active

508 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:

Detailed Rules Post

Be civil.
No spam.
Posts are to be related to self-hosting.
Don't duplicate the full text of your blog or readme if you're providing a link.
Submission headline should match the article title.
No trolling.
Promotion posts require active participation, with an account that is at least 30 days old. F/LOSS without a paywall has exceptions, with requirements. See the rules link for details. Tags [CBH] or [AIP] are required, see the links in Rule 8 for details.
AI-related discussions and AI-involved promotional posts have additional requirements for tagging, as noted in Rule 7 and the AI & Promotional Post Expanded Rules post, and find example disclosures here.

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 3 years ago

moderators

ruud@lemmy.world

Loki@lemmy.world

CannaVet@lemmy.world

devve@lemmy.world

ayyy@sh.itjust.works

curbstickle@anarchist.nexus

curbstickle_lw@lemmy.world

Just created my own zero trust network! (lemmy.world)

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

52 comments fedilink hide all child comments

No awards are needed, just wanted to share my excitement that while my Jellyfin server still keeps loosing my entire library every 24 hours at least now it has a domain and ssl cert!

That is all. Happy Friday everyone

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

[–] possiblylinux127@lemmy.zip 0 points 1 year ago (6 children)

You really shouldn't expose anything directly to the internet. It is a security problem waiting to happen. (Assuming it hasn't already)

This is how giant botnets form.

parent

hideshow 6 child comments

[–] dataprolet@lemmy.dbzer0.com 2 points 1 year ago (5 children)

What security problems?

parent

hideshow 5 child comments

[–] sugar_in_your_tea@sh.itjust.works 5 points 1 year ago (4 children)

Bots randomly attack stuff, and if you leave something insecure, they'll install a bot net node.

parent

hideshow 4 child comments

[–] dataprolet@lemmy.dbzer0.com -2 points 1 year ago (3 children)

Define "insecure".

parent

hideshow 3 child comments

[–] sugar_in_your_tea@sh.itjust.works 5 points 1 year ago (2 children)

Default passwords, old insecure versions of apps and system packages, etc. "Just getting it working" usually leaves things insecure, and you usually need to take things a step further to secure your publicly accessible services.

parent

hideshow 2 child comments

[–] SheeEttin@lemmy.zip 4 points 1 year ago (1 child)

Not just old insecure, but current insecure too. Plenty of stuff runs fully current but still vulnerable code. Put it behind a firewall.

parent

hideshow 1 child comment

[–] sugar_in_your_tea@sh.itjust.works 4 points 1 year ago

Sure. My point is that self-hosters tend to let services sit without updates for months if not years at a time. That's fine if you don't expose anything to the internet, so keep that surface area as limited as possible.

parent