view the rest of the comments
Selfhosted
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.
-
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!
@inquanto Theoretically, when you are alone in your own network it can be ok, to go only with http. But login passwords over http are transferred without encryption.
The problem with https are valid certificates, so that clients can connect to your selfhosted services without issues.
For example, I was not able to connect with a KDE PIM program to a Nextcloud with a self signed certificate or with http only.
With step-ca there can be a solution for this problem:
https://jan.wildeboer.net/2025/07/letsencrypt-homelab-stepca/
You could just use Let's encrypt
@possiblylinux127 Only when you have a valid domain name.
Not everybody can or wants to pay for a domain name, when it is not really necessary.
https://gen.xyz/pricing
Their cheapest domains are $1/year. I'm not sure I understand why you wouldn't just get a domain.
@possiblylinux127 A domain creates dependencies on external infrastructure.
Let's Encrypt and the Internet Security Research Group are U.S. organizations that rely on donations and can very likely be restricted by instructions from the American government.
Don’t get me wrong, if you want to use your own domain, you could do so.
But this creates dependencies for self-hosting, which may not be wanted and/or probably also not necessary.
So your solution is to use a less secure setup? I don't really get your logic. It is trivial to migrate acme providers and all your devices are already dependent on the global certificate authorities including Let's encrypt