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 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.
-
No low-effort posts. This is subjective and will largely be determined by the community member reports.
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
i've set up servers with static ips in datacenter settings before. the way you know you're online is usually that your cpu activity jumps a few percent from all the incoming ssh traffic from russia and china. i don't want to risk anything happening to my home server.
so fun to look through the ssh log and see hundreds of attempts...
Quick question: If I look through the ssh log and I don't see the hundred of attempts, what could be going on?..
I am not sure lol. perhaps your ssh port isn't exposed to the internet, or maybe the bots are just ignoring you? maybe your hosting provider has some sort of security process to reject those attempts preemptively?
I have no clue
Ignoring ? Nah someone mentionned my ISP might be protecting me uphill.
Are you not actually open to the public internet? Is it running on a nonstandard port? Is it already pwned and something is scrubbing logs?
Non standard port. But aren't secret chinese hack farm scanning wider than just 22 ? I don't know and deep down believe that it's pawned and scrubbing logs.
The resources required to port scan every port on every IP is generally not worth it. AFAIK they tend to stick to lower ports or popular ports. Unless they're intentionally targeting a specific IP or IP range, they're just looking for low hanging fruit.
Low hanging fruits are, in my personal case, pictures of my cats and public domain cultural artefacts.
Industrializing hacking of random servers sounds like a shitty idea at the end of the day...
The ability to generate a bunch of traffic that looks like it's coming from legit, every-day residential IPs is invaluable to disinformation campaigns. If they can get persistence in your network, they can toss it into a bot net which they'll sell access to on the dark web.
A sucker opens insecure services to the open internet every day, that's free real estate to bot farms. Only when the probability of finding them is low enough is it not worth the energy/network costs. I think hosting on non-standard ports is probably correlated with lowering that probability below some threshold where it becomes not worth it...don't quote me, though.
At the end of the day, the rule is not to depend on security by obscurity, but that doesn't mean never use it.
This whole thread (that I shamelessly hijacked) is very informative and allowed me to understand that cybersecurity is in practice a mixture of concrete nerdy log books and vague feeling of being under a threshold of worthiness.
I woke up this morning and there was a faint noise coming from the server: immediately thought "ok that's it, it's pawned and become a node in a vast grid of malicious bots"....it was a cron verification of drives
Hah yeah, I've definitely pulled the plug on my router before because I wasn't sure what I was seeing.
I mean, cybersecurity I would consider to be a research field. In practice, yeah, it's a bunch of people just doing their best.
I tend to keep everything inside my network and only expose what I need visible on non standard ports, one of those being a VPN. It's not that I couldn't run these services public facing, it's that the people taking the time to constantly update, configure, and auditing everything full time to head off red team are being paid. I don't need to deal with an attack surface any larger than it needs to be, ain't nobody got time for that.