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: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
No trolling.
-
Promotion posts require your active participation in selfhosting or related communities, or the post will be removed. No more than 10% of your posts or comments may be self-promotional, or your post will be removed. F/LOSS Exception: If your post is about a project that is completely open source & can be self-hosted in full without payment, and your account is at least 7 days old, your post is exempt from this rule as long as you continue to engage in comments.
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!
view the rest of the comments
You don't need to if you're just using things locally.
But also - domains are cheap.
yes you need if you want HTTPS that is accepted by the smartphone client apps of your services.
domains are a constant expense
They're cheap. You can also generate your own certs and use your own ca. But otherwise yes - quit yer bitching and learn how to do things right.
I do this, with a custom root cert, but it has problems. some apps don't accept it, some only accept it by totally disabling cert verification.
installation is also very cumbersome: you go to a weird, badly structured menu on your phone deep in the settings, and select the certificate from storage where apps could have had replaced it while you were navigating the menu.
it does not ask you for confirmation, does not show anything important about the cert, like its fingerprint you could use to quickly check its not been modified, any name constraints, validity period, etc. users cannot tell what that cert will grant its creator, because the system does not tell them anything so that they could decide, other than a generic "your connection may be monitored" message at all times. and when they refuse to install your cert, they are right, because this way it is very risky.
so please tell me "how to do things right", or shut up if you can't tell any useful info
WTF? I'm not trying to tell you how to do anything. I'm sick of selfhosted twerps bitching about "how hard it is to self host" when they think everything should be like an app on their phone. You need to learn how networks, dhcp, dns, ssl, certificates, etc. work.
guess what, I know how these work. running 2 dozens of services over two machines, and as I said above, I use my own root certificate... that's how I know that lots of apps have problems of varying severity with custom root certs! usage of user-installed certs is opt-in nowadays for smartphone apps, it's not at all like on windows or linux.
you are telling how to do things. the whole thread has been about you telling us to rent a domain for certificates and stop complaining about it being the only viable way...
Neat. I don't care.