Hello All,

I am really new to selfhosting, trying to learn the basics. I have a raspi 5 with docker installed and a domain. My question is, as I collect all my knowledge from all over the internet, is there a selfhosting guide for dummies? IT would be cool to have some guidance at hand to rfer to when i do dumb shit.

Thanks

  • ikidd@lemmy.worldEnglish
    42·
    10 days ago

    Don’t expose things to the internet with port forwards. Anything you want to do like that can be done with a reverse proxy or preferably a VPN.

    That is all.

    • werefreeatlast@lemmy.worldEnglish
      5·
      10 days ago

      It took me a while to learn that:

      Reverse proxy= your page lives in your basement but only your DNS knows. From outside everyone goes to “my page is cool.com”

      VPN= LAN but in WAN…go to Starfucks and you can still get your files from your basement’s NAS

      I’m sure they got other meanings, but this frame helped me a bit. Hide your IP!

    • WbrJr@lemmy.mlEnglish
      5·
      10 days ago

      But no ports only regards the home network, right? The proxy Server has to have open ports, and the home Server that connects to the proxy (how ever that’s done) needs to receive the forwarded packages on its ports, no?

      • ikidd@lemmy.worldEnglish
        2·
        10 days ago

        Yes. The proxy will have 80 and 443 forwarded from the router. Everything else gets proxied through your reverse so you can set basic auth on anything likely to be a security risk. Generally, you don’t want regular login pages exposed directly, they should be behind basic auth.

        • WbrJr@lemmy.mlEnglish
          1·
          3 days ago

          What i dont quite understand: If I use something like a next cloud client app or file manager integration, how would the authenticator work? I thought the app or program would nee d direct access to the service, without anything in front of it