Selfhosted

39919 readers

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

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.

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 1 year ago

MODERATORS

HybridSarcasm@lemmy.world

HybridSarcasm@lemmy.hybridsarcasm.xyz

Is it practically impossible for a newcomer selfhost without using centralised services, and get DDOSed or hacked? (lemmy.world)

submitted 4 months ago* (last edited 4 months ago) by Maroon@lemmy.world to c/selfhosted@lemmy.world

102 comments fedilink hide all child comments

I understand that people enter the world of self hosting for various reasons. I am trying to dip my toes in this ocean to try and get away from privacy-offending centralised services such as Google, Cloudflare, AWS, etc.

As I spend more time here, I realise that it is practically impossible; especially for a newcomer, to setup any any usable self hosted web service without relying on these corporate behemoths.

I wanted to have my own little static website and alongside that run Immich, but I find that without Cloudflare, Google, and AWS, I run the risk of getting DDOSed or hacked. Also, since the physical server will be hosted at my home (to avoid AWS), there is a serious risk of infecting all devices at home as well (currently reading about VLANS to avoid this).

Am I correct in thinking that avoiding these corporations is impossible (and make peace with this situation), or are there ways to circumvent these giants and still have a good experience self hosting and using web services, even as a newcomer (all without draining my pockets too much)?

Edit: I was working on a lot of misconceptions and still have a lot of learn. Thank you all for your answers.

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

[–] poVoq@slrpnk.net 34 points 4 months ago (6 children)

Don't leave SSH on port 22 open as there are a lot of crawlers for that, otherwise I really can't say I share your experience, and I have been self-hosting for years.

[–] jjlinux@lemmy.ml 3 points 4 months ago (5 children)

Am I missing something? Why would anyone leave SSH open outside the internal network?

All of my services have SSH disabled unless I need to do something, and then I only do it locally, and disable as soon as I'm done.

Note that I don't have a VPS anywhere.

[–] poVoq@slrpnk.net 5 points 4 months ago (2 children)

Some people want to be able to reach their server via SSH when they are not at home, but yes I agree in general that is not necessary when running a real home server.

[–] JustEnoughDucks@feddit.nl 5 points 4 months ago

Then use Wireguard to get into your local network. Simple as. All security risks that don't need to be accessed by the public (document servers, ssh, internal tools, etc...) can be accessed via VPN while the port forwarded servers are behind a reverse proxy, TLS, and an authentication layer like Authelia/authentik for things that only a small group needs to access.

Sorry, but there is 1 case in 10000 where a home user would have to have publicly exposed SSH and 9999 cases of 10000 where it is not needed at all and would only be done out of laziness or lack of knowledge of options.

load more comments (1 replies)

load more comments (3 replies)