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.

  • BearOfaTime@lemm.eeEnglish
    315·
    5 months ago

    What?

    I’ve popped up a web server and within a day had so many hits on the router (thousands per minute) that performance tanked.

    Yea, no, any exposed service will get hammered. Frankly I’m surprised that machine I setup didn’t get hacked.

    • poVoq@slrpnk.netEnglish
      21·
      5 months ago

      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.

      • youmaynotknow@lemmy.mlEnglish
        2·
        5 months ago

        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.netEnglish
          3·
          5 months ago

          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.nlEnglish
            1·
            5 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.

          • youmaynotknow@lemmy.mlEnglish
            1·
            5 months ago

            Yeah, I guess I’ve never needed to do that. That may change as I’m thinking of moving all my services from UnRaid to ProxMox to leave UnRaid for storage only.

            I guess that’ll bring me back here soon enough.

    • Count042@lemmy.mlEnglish
      4·
      5 months ago

      I’ve been self-hosting a bunch of stuff for over a decade now, and have not had that issue.

      Except for a matrix server with open registration for a community that others not in the community started to use.

    • MangoPenguin@lemmy.blahaj.zoneEnglish
      1·
      5 months ago

      I can’t say I’ve seen anything like that on the webservers I’ve exposed to the internet. But it could vary based on the IP you have if it’s a target for something already I suppose.

      Frankly I’m surprised that machine I setup didn’t get hacked.

      How could it if all you had was a basic webserver running?