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 30 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
For remote management, I just enable SSH, configure it to run on some non-standard port and enable Fail2ban... Make sure I use certificates or secure passwords and also check if fail2ban is actually doing its job. Never had any issues with that setup.
For the services I'll either use a reverse proxy, plus configure the applications not to allow infinite login attempts, or Wireguard / a VPN.
This is what I've done for years, but I sometimes feel like it's not a great solution from a security standpoint.
Though I have switched from fail2ban to Crowdsec, which did end up banning my own connection attempts when I forgot to whitelist myself, so that seems secure enough.
Hmmh. I'm not entirely satisfied with any of them. Crowdsec is a bit too complex and involved for my taste. And oftentimes there's no good application config floating around on the internet, neither do I get any sane defaults from my Linux distribution. Whereas fail2ban is old and eats up way too much resources for what it's doing. And all of it is a bit too error-prone(?) As far as I remember I had several instances when I thought I had set it up correctly, but it didn't match anything. Or it was looking for some logfile per default but my program wrote to the SystemD journal. So nowadays, I'll double-check everything. I wish programs like sshd and webapps came with that kind of security built in in some foolproof way.