this post was submitted on 11 Aug 2023
26 points (96.4% liked)

Selfhosted

40296 readers
428 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
 

I'm just a novice at self hosting and I see a lot of talk about the risks of exposing stuff to the world. Here's my setup:

-Rpi4 hosting Overseerr
-Desktop computer hosting Nginx and some Cloudflare DDNS update containers

Cloudflare directs request.domain.com to my home IP address. Nginx forces HTTPS and directs the request to the Pi.

Is there any risk in this setup or are there more steps I can take to secure it?

you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 2 points 1 year ago

Anything on the public internet is some amount of risk.

It sounds reasonably configured, and for a single service that's been fairly robust, the only thing you really should make sure you're doing is updates - better if you configure automatic updates, so you don't even have to think about it.

unattended-upgrades is what you'd want on a Debian-alike for updates, and Overseerr depends on how you installed it.