Comment

Comment on Beginner looking for advice on open-source NAS hardware and OS for self-hosting

hperrin@lemmy.ca ⁨3⁩ ⁨hours⁩ ago

From now on, whenever you set up a service, you’ll use a subdomain, and you’ll point it in dns as a CNAME record at your apex domain (usually just an @ symbol in the input box). You’ll then (if it’s a web service) create a proxy in NPM pointed at whatever port you give it.

So now you wanna create a WireGuard vpn, so you can securely access your own stuff from your own devices outside your house. (I’d recommend not opening every service up to the internet.)

github.com/linuxserver/docker-wireguard

That one can be tricky, but ultimately you should have a file (or QR code) that you can put on your phone in the WireGuard app that will give you vpn access. Remember to set up a CNAME for your subdomain (something like vpn.example.com). Although, for this, it would be fine to use the apex domain.

So now you can set up a Nextcloud and an Immich stack. Put them on an unused port, then point a proxy for their subdomain at that port (127.0.0.1:2201 or whatever), add your SSL cert, and you’re good.

[continued…]

source

Sort:hotnew top

hperrin@lemmy.ca ⁨3⁩ ⁨hours⁩ ago
In NPM, set up an access list like this:

Image

Last one should be your public IP address, with “/32” on the end.

Use this access list for all services you don’t want the wider internet to see (probably all of them for you). With this setup, you can still open a service, if you want, but normally you’ll need to be on your VPN to see it from outside your house.

source
- hperrin@lemmy.ca ⁨3⁩ ⁨hours⁩ ago
  Every once in a while, you should run these commands in each services folder:
  
  docker compose pull docker compose up -d # check if everything is still good docker system prune -a
  
  You should also back up your services folder regularly. That’s beyond the scope of this Lemmy comment, though.
  
  source