this post was submitted on 15 Nov 2024
49 points (96.2% liked)

Selfhosted

40347 readers
339 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:

  1. Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.

  2. No spam posting.

  3. 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.

  4. Don't duplicate the full text of your blog or github here. Just post the link for folks to click.

  5. Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).

  6. No trolling.

Resources:

Any issues on the community? Report it using the report flag.

Questions? DM the mods!

founded 1 year ago
MODERATORS
 

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

you are viewing a single comment's thread
view the rest of the comments
[–] ikidd@lemmy.world 2 points 1 week ago (2 children)

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.world 5 points 1 week 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.ml 5 points 1 week ago (1 children)

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.world 2 points 1 week ago (1 children)

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.ml 1 points 2 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